You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I use plugin types for custom API without any registered message processing step. Unfortunately, the creation of the Xrm instance fails because the plugin type is not recognized in the metadata. If I check the assembly in the online instance the plugin type exists. Creating a step on the plugin will affect the metadata created with the creation tool... so possibly a "dummy step" could solve the issue.
To Reproduce
Create and register a Plugin without any step online
Create the metadata for this online instance
The creation of the instance fails with error message: "OneTimeSetUp: DG.Tools.XrmMockup.MockupException : Unknown plugin 'Plgin name', please use DAXIF registration or make sure the plugin is uploaded to CRM."
Expected behavior
The metadata tool should create the plugin metadata or plugins without message processing steps should be ignored on cretaing the instance
Environment
D365 online
Tool version: 1.13.3
The text was updated successfully, but these errors were encountered:
DAXIF has a CustomAPI base class which should be extended in CustomAPI implementations, and which XrmMockup will recognize.
Once it has been extended, you can then register the API in the constructor using the same logic as for plugins, and they will be automatically handled in the PluginSync functionality.
Example (see the CustomAPI class for supported methods, unfortunately the Wiki doesn't seem to be updated):
Describe the bug
I use plugin types for custom API without any registered message processing step. Unfortunately, the creation of the Xrm instance fails because the plugin type is not recognized in the metadata. If I check the assembly in the online instance the plugin type exists. Creating a step on the plugin will affect the metadata created with the creation tool... so possibly a "dummy step" could solve the issue.
To Reproduce
Expected behavior
The metadata tool should create the plugin metadata or plugins without message processing steps should be ignored on cretaing the instance
Environment
The text was updated successfully, but these errors were encountered: