Dynamics Community Forum Thread Details

Issue with Registering Step for Extending Copilot for Sales in Dynamics 365

I followed the documentation for extending Copilot for Sales in Dynamics 365 and made the necessary code changes. While registering an assembly, I encountered an issue:

The SDK Message list does not display the name "msdyn_SalesExtendedSummaryProvider" when registering the step.
While troubleshooting, I found that the properties/fields of the entity have the following values:
- isPrivate: true
- workStepEnabled: false

My Questions:

Could these properties be the reason why the SDK Message is not appearing in the list?
Is there a way to update the entity (which is read-only)?
- I attempted to modify it using a custom connector, Power Automate flow, and a plugin, but none were successful.
Is this something Microsoft can update on their end?
Any alternative solutions to register the step successfully?

Any insights or solutions would be greatly appreciated!

Categories:

Other

“AI was used in this reply”.
The issue you are facing—where the SDK Message "msdyn_SalesExtendedSummaryProvider" does not appear in the list while registering the step—is likely due to the configuration settings of the Custom API you created. Based on the provided JSON data, here are the key potential causes and solutions:
Possible Causes & Solutions:

Custom API is Marked as Private ("isprivate": true)
- Issue: The "isprivate": true property means that this Custom API is not available for use outside of its internal implementation.
- Solution: Change this property to "isprivate": false so that the message is exposed and can be used in a plugin step.
- How to Fix:
  1. Open Power Apps Maker Portal.
  2. Navigate to Solutions → Locate your solution.
  3. Open the Custom API (msdyn_SalesExtendedSummaryProvider).
  4. Set "Is Private" to No.
  5. Save and publish the changes.
SDK Message is Not Workflow-Enabled ("workflowsdkstepenabled": false)
- Issue: The "workflowsdkstepenabled": false setting means that the Custom API does not allow workflows, including plugin steps.
- Solution: Set this property to true so that the API can be used in a plugin.
- How to Fix:
  1. Open the Custom API record in Power Apps.
  2. Find the "Enable for Workflow" (or "Workflow SDK Step Enabled") setting.
  3. Change it to Yes.
  4. Save and publish the changes.
Availability is Set to 0 ("availability": 0)
- Issue: "availability": 0 means the Custom API is only available internally and not for external use in plugins.
- Solution: Change Availability to 2 (Global).
- How to Fix:
  1. Open the Custom API in Power Apps.
  2. Locate the Availability field.
  3. Change its value to 2 (Global).
  4. Save and publish.

Final Steps to Verify the Fix:

After making the above changes, publish all customizations.
Close and reopen the Plugin Registration Tool.
Try registering the step again and check if "msdyn_SalesExtendedSummaryProvider" appears in the list.

These changes should resolve your issue and allow you to register the step successfully.

Quick Links

Leaderboard