Supported messages and entities for plug-ins
Applies to Dynamics 365 for Customer Engagement apps version 9.x
This topic identifies the message and entity combinations that support offline execution of plug-ins for Dynamics 365 for Microsoft Office Outlook with Offline Access. For information on server registered plug-ins that do not require offline execution, see Available events.
The Message Availability column of the table shown below indicates whether a message is available online, offline, or both. The Entity Deployment column indicates if the entity can be deployed on the server, on the client, or both. A value of null in the Primary Entity column means that there is no primary entity associated with the message. The same applies to the Secondary Entity column.
In plug-in code, you can send any message to the web services except those messages that create or update metadata.
Custom entities support the same base messages as system entities, depending on whether the entity is organization-owned or user-owned. For more information, see Actions on Entity Records.
The term offline applies to the Dynamics 365 for Microsoft Office Outlook with Offline Access. The term client can apply to either Dynamics 365 for Outlook Online or Dynamics 365 for Microsoft Office Outlook with Offline Access.
Whether a message is available online or offline can be determined programmatically or through a query by inspecting the
SdkMessage.Availability attribute. To view the entity metadata for your organization, install the Metadata Browser solution described in Browse the metadata for your organization. You can also browse the reference documentation for entities in the Entity Reference.
Supported messages for custom entities
Custom entities can be either organization-owned or user-owned, which defines the set of messages available for the entity. The following table lists the messages for custom entities that support the execution of plug-ins.
|Message Name||Ownership Type||Message Availability||Entity Supported Deployment|
|Assign||User-owned entities only||Server||Server|
|Create||User-owned and organization-owned entities||Both||Server|
|Delete||User-owned and organization-owned entities||Both||Server|
|GrantAccess||User-owned entities only||Server||Server|
|ModifyAccess||User-owned entities only||Server||Server|
|Retrieve||User-owned and organization-owned entities||Both||Server|
|RetrieveMultiple||User-owned and organization-owned entities||Both||Server|
|RetrievePrincipalAccess||User-owned entities only||Both||Server|
|RetrieveSharedPrincipalsAndAccess||User-owned entities only||Both||Server|
|RevokeAccess||User-owned entities only||Server||Server|
|SetState||User-owned and organization-owned entities||Both||Server|
|Update||User-owned and organization-owned entities||Both||Server|
Supported messages for default entities
Before you consider writing a plug-in, you should verify that the target message and entity request supports the execution of plug-ins. Since Dynamics 365 is periodically updated with new messages and entities, it is best to query the organization for this information. This can be done using the Plug-in registration tool or running a fetchXML query as described below.
To verify if a message and entity combination supports execution of plug-ins using the Plug-in Registration tool, follow these steps.
- Run the tool and connect to a D365 organization.
- In the Registered Plug-ins & Custom Workflow Activities list, expand an assembly that contains registered plug-ins. You can even do this step on a system assembly since you will not actually be completing the step registration.
- Right-click on a plug-in in the list and choose Register New Step.
- Enter the target message and primary entity in the appropriate fields to see if that combination is supported for plug-in registration.
- Cancel (close) the step registration form and exit the tool.
To verify if a message and entity combination supports execution of plug-ins using a database query, use Advanced Find or a community tool (e.g., FetchXML Builder) to execute the following fetchXML query. When using Advanced Find, you must create the query interactively.
For Outlook client offline plug-ins:
<fetch> <entity name='sdkmessage' > <attribute name='name' /> <link-entity name='sdkmessagefilter' alias='filter' to='sdkmessageid' from='sdkmessageid' link-type='inner' > <filter type='and' > <condition attribute='iscustomprocessingstepallowed' operator='eq' value='1' /> <condition attribute='isvisible' operator='eq' value='1' /> <condition attribute='availability' operator='ne' value='0' /> </filter> <attribute name='primaryobjecttypecode' /> </link-entity> <filter> <condition attribute='isprivate' operator='eq' value='0' /> <condition attribute='name' operator='not-in' > <value>SetStateDynamicEntity</value> <value>RemoveRelated</value> <value>SetRelated</value> <value>Execute</value> </condition> </filter> <order attribute='name' /> </entity> </fetch>
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.