PL-400 · Question #361
You create a custom API. You define the API as a function. The custom API does not appear in the response received from https://[yourorg].api.crm.dynamics.com/api/data/v9.2/$metadata and returns an…
The correct answer is D. Set the is Private property of the custom API to False. If you aren't willing to support other developers using your custom API, you should set the custom API Is Private (IsPrivate) property to true before you ship the managed solution containing your The Is Private property blocks the custom API from appearing within the $metadata…
Question
Options
- AAdd a response property to the custom API.
- BAdd a request property to the custom API.
- CSet the Enabled for Workflow option of the customer API to True.
- DSet the is Private property of the custom API to False.
How the community answered
(21 responses)- A5% (1)
- C10% (2)
- D86% (18)
Explanation
If you aren't willing to support other developers using your custom API, you should set the custom API Is Private (IsPrivate) property to true before you ship the managed solution containing your The Is Private property blocks the custom API from appearing within the $metadata service document and prevent Dataverse code generation tools from creating classes to use the messages for your custom API. https://learn.microsoft.com/en-us/power-apps/developer/data-platform/custom-api
Community Discussion
No community discussion yet for this question.