Secondary
Entity:
"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".
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.
GAC
Databse and Disk Deployments:
GAC
|
Database
|
Disk
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
You
can refer external DLL assemblies from the disk and from GAC
|
CRM
Plugin Run In User's Context:
http://anythingcrm.blogspot.in/2013/08/crm-2011-impersonation-in-plug-ins.html
----------------------------------------------------------------------------------------------------------------------------------------
Execution
Order
Execution
order in plugin specifies the order, also known as rank, that
plug-ins are executed within a pipeline stage
Plug-ins registered with an order value of 1 are executed first,
followed by plug-ins registered with an order of 2, and so on.
However, if there is more than one plug-in in a stage with the same
order value, then the plug-in with the earliest compilation date is
called first.
------------------------------------------------------------------------------------------------------------
Event
Pipeline OF Stages
http://plugincrm2011.blogspot.in/2013/01/plug-in-event-execution-pipeline.html
------------------------------------------------------------------------------------------------------------
Unsecure
Configuration
Unsecure configuration
information could be read by any user in CRM. Remember
its public information (Eg: Parameter strings to be
used in plugin could be supplied here)
Imagine
that you include a plugin, plugin steps and activate them in a
solution. Later solution was exported as Managed Solution to another
environment. In this scenario, the supplied Unsecure configuration
values would be available in the new environment
------------------------------------------------------------------------------------------------------------
Secure
Configuration
The Secure Configuration
information could be read only by CRM Administrators.(Eg:
Restricted data from normal user could be supplied here)
Imagine
that you include a plugin,plugin steps and activate them in
asolution. Later solution was exported as Managed Solution to
another environment. In this scenario, the supplied Secure
configuration information wouldNOT be available in
the new environment. The simple reason behind this is to
provide more security to the contents of Secure
Configuration.
------------------------------------------------------------------------------------------------------------
No comments:
Post a Comment