Landing on a parashutes to the unknown world(at least to me) of Microsoft Dynamics CRM.
The first thing I'm told is that I'm in charge of developing the functionality for the mails delivery.
Well after some days having no clue what to do and annoying some colleagues (witc I'm very grateful from their help) with my constant questions after some frustrating hours of not moving forward. I start finally developing my first customized workflow.
Thrusting in my coding for the workflow wich seems very simple I decide its time to publish it on the CRM to be used there.
Here is where my headaches started. I was not able to register after many attepmts the WF until i find this error while debugging the "plugindeveloper" (the tool used to register workflows on the crm) the error I found after some tracking was "The type Lookup of the property contacto_p is not supported". Where "contacto_p" its an CrmInput variable of the type Lookup.
Remeber "Lookup". Well Lookup turns out to be a class that exists on both the sdk and the webreference (the personalized entities) library.
Having not much idea of wich one to use I starting trying with them declaring the contacto_p var using one or another type until voilá! The workflow has been registered succesfully!
Happy with this I move to my next assignment to use the customized workflow to configure the bussiness logic on the application. First step is to call the wf from the application.
Another headache started! I cannot publish the worfklow so it can be executed!
The friendly but not really helpfull error message was:
"An error occurred when the workflow was being created. Try to save the workflow again."
Being frustrated again after commenting almost all the code and attempting many solutions.
I call for help to my friend Victor who gently starts helping me. Well at this point he must have been annoyed by me.
Untill he finds this forum where they had exactly the same problem and some Anonymous9040600 replies. That was it! The infamous Lookup!
I realized immediatly after reading his post that he had the answer. I remmebered the suffering with the registering and then I find this on my code:
- The CrmInput var was declared as a sdk Lookup.
- The line where the function DependencyProperty.Register is used the propertyType parameter was calling to the type of the webreference Lookup.
The solution use the same type of object to obtain the DependencyProperty as the one used on the CrmInput or CrmOutput.
As this was the first post for this blog I decided to make it more dramatic but I promise to deliver more tecnical posts for all the unusual or common problems I'm encountering during my stay at the Microsoft Dynamics world.
'till next post!
viernes, 25 de septiembre de 2009
Suscribirse a:
Entradas (Atom)
