Recently, I was working on creating a custom connector that has got one action which is a GET request and accepts parameters. The purpose was to use this custom connector in Power Automate which could then have been executed on demand or create/update of record. Below is the definition of custom connector: And here’s the request details(Used Import from sample to construct this): Verb: GET URL: CalculateRollupField(Target=@target,FieldName=@fieldName)?@target={‘@odata.id’:’accounts(96ca73be-14e5-eb11-bacb-0022481016fb)’}&@fieldName=’new_noofcontacts’ I have passed 2 parameters in the URL ..read more

In this blog, we’ll see how to create custom API in maker portal and write plugin to implement it. We’ll take the example of refreshing roll up field on demand. This API will take 3 parameters: TargetEntity: Name of the entity containing the roll up field TargetId: GUID of the record Field: Name of the roll up field to be refreshed In the plugin we’ll write the code to execute request to refresh roll up field. We’ll test the custom API using Postman. So, let’s get started. Go to Solutions -> Click on New -> Select Custom API. Fill the details of the custom API record as shown below ..read more

To enable Microsoft Teams in D365, Go to Settings –> Administration –> System Settings –> General Tab and flip the below highlighted options to Yes. Once done, we’ll be able to see Collaborate button on the ribbon as shown below. By default it’ll be enabled on several OOB entities as mentioned here: https://docs.microsoft.com/en-us/dynamics365/teams-integration/teams-collaboration#record-types-that-support-microsoft-teams-integration However, we can also enable it on custom entity programmatically. Below is the screenshot of a custom entity “new_cidproduct” before enabling Teams in ..read more

Recently, we copied a production environment to sandbox environment. Then, I was working on a requirement on the sandbox environment for which I created a power automate. The trigger was on create of a record. After creating the power automate, when I tested the functionality, for some reason the power automate was not getting triggered at all. After going through the power automate several times, I couldn’t find anything suspicious. Then, I thought something was fishy. Just to verify nothing’s wrong with the environment, I created a simple power automate on create of Contact record. Eventual ..read more

Recently, while importing a solution to target instance, we got an error saying “The datafieldname attribute sab_disablerecordon for control is not valid for create” and the solution import failed. After investigating this issue, we figured out that in the source environment, the field ” sab_disablerecordon ” was used on Quick create form for that entity. Also, this field is a calculated field which doesn’t make sense to be put on a quick create form. Removing this field from the quick create form, exporting the solution and importing it again to target instance worked this time. Hope it helps ..read more

Recently, we were working on Power Automate where we were supposed to set a variable for further use based on the value of an option set field in an entity. We used Switch action and inside Case block we were trying to set the variable as shown below: While executing the Power Automate, unfortunately, we were getting error: Action ‘Set_Claim_Type_REPW’ failed. Surprisingly, there was no additional details to the error message for which we spent significant amount of time finding the root cause. We tried to tweak the sequence of Set Variable action and it was working fine. So, we made sure tha ..read more

Recently, while deploying Azure Function from Visual Studio, we got an error “Web Deploy cannot modify the file on the Destination because it is locked by an external process”. To fix this issue, we created an application setting. There are 2 ways to do this: Create an Application Setting in the Function App in Azure portal: MSDEPLOY_RENAME_LOCKED_FILES = 1 Or, 2. Create and Application Setting in the Publish profile for the respective Function App in Visual Studio. Click on Manage Azure App Service Settings. Click on Add Setting -> Add setting named “MSDEPLOY_RENAME_LOCKED_FILES ..read more

In this post, we’ll see how we can perform aggregate function on data such as Sum or Count using PowerAutomate. Unlike LINQ in C# or SQL, it’s not very straight forward to do using PowerAutomate for which I thought of sharing the approach we had taken. Recently, we got a requirement to calculate the sum of Quantity, after grouping the data on 5 columns NDISNumber, SupportDeliveredFrom, SupportNumber, ClaimType and CancellationReason in a custom entity Claim. Below are the steps we followed to achieve the result: Action: Initialize Variable(Variable) Purpose: Hold the unique data of 5 columns b ..read more

We often come across requirements in which we want to add certain value to the same variable e.g. for integer variable, x=x+5 or for string variable, test=test+”additional”. We were trying to achieve the same thing using PowerAutomate. However, while doing this using Set Variable action, we got an error saying “Self-reference is not supported when updating the value of variable”. Below is what we were trying to do inside Apply to each action and the expression is: add(variables(‘Service Delivery Type Total Amount’),items(‘Apply_to_each_Service_Delivery_Type’)?[‘dxc_amount ..read more

Recently, while activating a Business Process Flow, we got below error: “An attribute with the specified name already exists. Exception Message: Column names in each table must be unique. Column name ‘stageid’ in table ‘EntityName’ is specified more than once.” While checking the entity metadata for which we had created BPF, we found that Business Process Flows was unchecked. After ticking the checkbox, we saved the entity and published it. Then, we tried to activate the BPF again and it worked. Hope it helps ..read more