<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Dataverse-Customapi on It Must Be Code!</title><link>https://itmustbecode.com/tags/dataverse-customapi/</link><description>Recent content in Dataverse-Customapi on It Must Be Code!</description><generator>Hugo</generator><language>en-CA</language><lastBuildDate>Thu, 25 Mar 2021 21:45:30 +0000</lastBuildDate><atom:link href="https://itmustbecode.com/tags/dataverse-customapi/feed.xml" rel="self" type="application/rss+xml"/><item><title>Dataverse Custom API: Function (GET) vs Action (POST)</title><link>https://itmustbecode.com/dataverse-custom-api-function-get-vs-action-post/</link><pubDate>Thu, 25 Mar 2021 21:45:30 +0000</pubDate><guid isPermaLink="false">https://itmustbecode.com/dataverse-custom-api-function-get-vs-action-post/</guid><description>&lt;p&gt;The new &lt;strong&gt;Dataverse Custom API&lt;/strong&gt; feature ( &lt;em&gt;now in General Availability&lt;/em&gt; 🚀) empowers developers with the ability to create their own &lt;strong&gt;custom messages&lt;/strong&gt; to extends the capabilities of the &lt;strong&gt;Power Platform.&lt;/strong&gt; These custom messages are then exposed by the Dataverse endpoints (WebApi and Organizationservice) like other out-of-the-box messages (Create, Update, etc..).&lt;/p&gt;
&lt;p&gt;While the &lt;strong&gt;Custom API model&lt;/strong&gt; shares a lot of similarities with the traditional &lt;strong&gt;Custom Action model&lt;/strong&gt; that is available since Dynamics 2013, it also exposes a bunch of &lt;strong&gt;unique features&lt;/strong&gt; that are worth taking a look at.&lt;/p&gt;</description></item><item><title>Dataverse Custom API: AllowCustomProcessing Explained</title><link>https://itmustbecode.com/dataverse-custom-api-allowcustomprocessing-explained/</link><pubDate>Mon, 11 Jan 2021 12:58:32 +0000</pubDate><guid isPermaLink="false">https://itmustbecode.com/dataverse-custom-api-allowcustomprocessing-explained/</guid><description>&lt;p&gt;This is the first article in a series of posts aimed at showing the &lt;strong&gt;main differences&lt;/strong&gt; between &lt;strong&gt;Dataverse Custom API&lt;/strong&gt; s and the more traditional &lt;strong&gt;Workflow Custom Actions&lt;/strong&gt;. This article will focus on the &lt;strong&gt;AllowedCustomProcessingStep&lt;/strong&gt; attribute of Custom APIs.&lt;/p&gt;
&lt;h2 id="custom-api-vs-custom-action"&gt;Custom API vs Custom Action
&lt;/h2&gt;&lt;p&gt;Dataverse &lt;strong&gt;Custom APIs&lt;/strong&gt; and Workflow &lt;strong&gt;Custom Action&lt;/strong&gt; share common ground. The 2 models will expose &lt;strong&gt;custom Messages&lt;/strong&gt; that can be called by the &lt;strong&gt;Dataverse WebApi&lt;/strong&gt; like other Out-of-the-Box Messages of the Platform (ex. Create, Update). The differences are found in the underlying implementation of each model.&lt;/p&gt;</description></item></channel></rss>