You are a Dynamics CRM 2011/2013 Developer and you need to develop some plugnis to perform some synchronous/asynchronous operations that need realy a plugin development. You develop your plugins on Visual Studio and you build. You build succesfully your plugins assembly and all seems fine. You use Plugin Registration Tool (PRT) to register your plugin, steps and images. And Now you are doing your test on your records to verify if your plugins works fine or not, and like for me, nothing works from the first time :) So you had a Busines Process Error and you want to know why ? It means, you should debug your code. And There is three ways to do it : - First way : If you are using a OnPremise version of Dynamics CRM 2011/2013 and you have your own development server with Visual Studio: * you should copy your code in your server * open it with Visual Studio * put your breakpoints * attach w3p process * And debug When it's ok you can copy yo...
"Secondary Entity use when you have to trigger plugin or retrieve record from Intersect Entity(contactleads) having records of Entities(Contact and Lead) having N:N Relationship" While using the Plugin Registration tool in Dynamics CRM, we might have rarely or even never used the ‘Secondary Entity’ field and almost always assigned it as ‘none’, but there are some scenarios where this field comes into play. When is ‘Secondary Entity’ required The following 2 messages require the ‘Secondary Entity’ to be specified while registering a step in Plugin registration: SetRelated RemoveRelated These two methods were extensively used in Dynamics CRM 4.0, but they were deprecated from Dynamics CRM 2011 onwards; although you can still use them in 2011 and 2013.
I get asked about many-to-many (a.k.a. N:N) relationships more than just about any other single topic, so here’s a summary of how they work in Dynamics CRM 2011. I’ll review both “native” and “manual” N:N’s, using a simple Association to Contact relationship to illustrate. This is a classic many-to-many: each association should be able to have multiple contacts associated with it, and each contact should in turn be able to be associated with many associations. Native N:N Relationships With native N:N relationships, you open up an entity for customization, click the N:N relationships link, and click the New Many to Many Relationship button and select the entity to create the relationship to. For the Association to Contact N:N relationship, I’ll start from the Association entity: In the previous figure, notice that Do no Display is selected in the Display Option for each side. I only show that to illustrate a point: what this will do is prevent the relationship from be...
Comments
Post a Comment
Hi,
If any one want to give the stagnation and change its most welcome.
Thanks!!
Rajesh Singh.