We might below error in our flow –
BadRequest. Http request failed as there is an error: ‘Cannot write more bytes to the buffer than the configured maximum buffer size: 104857600.’.
This is because of the 100 MB Message Size limits in Power Automate.
We can enable Allow chunking option if supported by the action.
Or we can fix it by specifying Select columns and Filter Rows to limit the data returned as in the case of the List Rows action of Dataverse.
Hope it helps..
Within the Maker Portal, we can only turn on / turn off one cloud flow at a time.
If we select multiple flows, we do not see that option.
Here we can make use of XrmToolBox’s Bulk Data Update plugin.
Get the required cloud flows to be disabled from the Workflow table having Category as Modern Flow.
Select the required cloud flows (or all flows returned), navigate to the Set State tab, and set the appropriate Status and click on Update records.
Or, from the Advanced Find also we can look for the Processes with the Category as the Modern Flow
And use Activate and Deactivate options (here for a few flows we faced issues while trying to activate even though we used the proper account for doing so)
Hope it helps..
We recently had a requirement to create the SharePoint folder automatically on the Account records creation, instead of having the users click on the Documents tab to create it.
We could write a Power Automate flow to achieve this.
Here we have enabled the Share Point server-based integration. Also, the SharePoint Site and the main or parent folder for the Account are already created/configured.
Below is the corresponding Document location record for the parent Account folder.
Below is how our Flow will look like –
2. Create a new folder inside Account Folder, here for the name of the folder we are using the format “AccountName_AccountNumber“
3. Create a new Document Location record, associating the Account document location with the parent location record. Here we are specifying the same folder name in the relative URL.
We can also fetch the GUID of the Account document location and/or use a variable to store the GUID.
4. Lastly, we are associating these 2 new records.
Below is our newly created account record.
Below we can see our flow ran successfully.
We can see the new folder created and associated.
Here if we click the Documents tab immediately after creating the account record, before our flow runs, we might have the OOB folder also getting created along with our custom folder (flow being asynchronous). If our custom folder is already created and associated before the user clicks on the documents tab, then CRM will not be creating a new folder.
Hope it helps..
We had one flow on the creation of an account record, our flow was running fine, and then we made a few changes to it and saved it, after which it stopped getting triggered.
We could not figure out why it was not getting triggered so eventually we tried changing the Trigger Type to Added or Modified or Deleted, just to see if that will trigger it.
It ran this time on create of account record.
After which we changed it back to Added, the original definition.
And from that point onwards it was getting triggered as expected.
Also make sure if the Admin mode is turned off.
Hope it helps..
Below is the sample flow we can use to retrieve the Required (requiredattendees) field’s value from the Meeting table (on the update of the record).
Here we are triggering the flow, if there is an update in the subject field of the meeting record.
Then using the List rows action we are fetching the Activity Parties record associated using the Appointment’s unique identifier and participation mask as 5.
More on participation type mask –
And in the last step, we are checking for all the associated Activity Party GUIDs for a specific GUID and then update the record or cancel the record.
Hope it helps..
Recently we were exploring the possibility of creating a marketing form submission record through flow/custom code. Here simply creating the marketing form submission record is not enough, for it to be processed by the platform, we need to call the bound action – msdyncrm_UpdateMarketingFormSubmission with Step = Retry. (And it’s all not an officially supported scenario, so be careful)
Below is how the flow looks like
First, we create a form submission record – 
After creating the form submission record, we are creating and associating the marketing field submission records with the values that we want to pass for the form – email, first name, and last name in this case.
And then eventually calling the action –msdyncrm_UpdateMarketingFormSubmission to trigger the submission (resubmit) of the form submission record.
On running the flow, we can see the record created with the status as pending.
Within a few seconds, if the input is correct, we can see the status updated as success
and the corresponding contact/lead created or updated.
Hope it helps..
Nishant Rana's Weblog 