Disable Hyperlink for Lookup Columns in Grid Views of Model-driven Apps
This post will explain how you can turn off clickable lookups in the grid views of model-driven apps. Microsoft has recently rolled out the new update for Power Apps Read-Only Grid which has a new property called “Navigation types allowed”. This property will allow the system customiser to disable clickable hyperlinks for the lookup column values and only show them as text. According to… Continue Reading...
Filter by Lookup with retrieveMultipleRecords JavaScript WebApi in Offline Mode
This post will explain how filtering using the lookup column is different between a normal online scenario and a mobile offline scenario in Xrm.WebApi.retrieveMultipleRecords. You will also learn about how to write a script to support both scenarios. Before setting up the Dynamics 365 app or Power Apps model-driven app in offline mode, it is important to read through this… Continue Reading noreply@blogger.com (Linn Zaw...
Managing Public SharePoint Documents for Power Apps Portal and Internal Documents Using Cloud Flow (Part 8 of 8)
<meta content="When the SharePoint integration from Power Apps portals is enabled, the users can see all the SharePoint documents related to the record but we can upload the documents for internal purpose to the secondary Document Location and keep those hidden from the Portal user.” name=”twitter:description”> This is the eighth post in a series of Automating SharePoint Integration with …...
Automatically Create SharePoint Folder Structure Based on Specific Table in Dataverse Using Cloud Flow (Part 3 of 7)
This is the third post in a series of Automating SharePoint Integration with Dataverse using Power Automate. You can check out the other posts via these links (Part 1, Part 2, Part 4, Part 5, Part 6, Part7) In my first post, I have explained how to automatically create the SharePoint Document Location using the cloud flow when a new row is added to the Dataverse/Dynamics 365 table. But if you… Continue Reading...
Trigger OnCreate Cloud Flow for Existing Rows (Part 2 of 7)
This is the second post in a series of Automating SharePoint Integration with Dataverse using Power Automate. You can check out the other posts via these links (Part 1, Part 3, Part 4, Part 5, Part 6, Part7) In my previous post, I have explained how to automatically create the SharePoint Document Location using the cloud flow when a new row is added to the Dataverse/Dynamics 365 table. But if… Continue...
Find SharePoint Folder with Particular Name Among Multiple Document Libraries Using Cloud Flow (Part 7 of 7)
This is the seventh post in a series of Automating SharePoint Integration with Dataverse using Power Automate. You can check out the other posts via these links (Part 1, Part 2, Part 3, Part 4, Part 5, Part 6) In the Part 3 post, I have explained how to automatically create subfolders under the Document Library. If the requirement is to process/send the documents stored in one of… Continue Reading...
Automatically Move Dataverse Email Attachments to SharePoint Document Library Using Cloud Flow (Part 6 of 6)
This is the sixth post in a series of Automating SharePoint Integration with Dataverse using Power Automate. You can check out the other posts via these links (Part 1, Part 2, Part 3, Part 4, Part 5) With server-side synchronisation, you can synchronise your email system with Microsoft Dataverse and create corresponding email activities in Dataverse. But if the option to… Continue Reading noreply@blogger.com (Linn Zaw...
SharePoint URL Shortcut on Form and Generic Dataverse Update Step in Power Automate (Part 5 of 6)
This is the fifth post in a series of Automating SharePoint Integration with Dataverse using Power Automate. You can check out the other posts via these links (Part 1, Part 2, Part 3, Part 4, Part 6) SharePoint integration in a model-driven app is easy to use and the user can simply view/upload the related documents in the Documents associated grid under the Related tab. But the… Continue Reading noreply@blogger.com (Linn Zaw...
Automatically Create SharePoint Subfolders Using Cloud Flow and Environment Variable (Part 4 of 6)
This is the fourth post in a series of Automating SharePoint Integration with Dataverse using Power Automate. You can check out the other posts via these links (Part 1, Part 2, Part 3, Part 5, Part 6) In some of my projects, there is a requirement to automatically create subfolders when the document location is created. In that way, the users will have a proper folder structure to… Continue Reading noreply@blogger.com (Linn Zaw...
Get Output Data from Expand Query of Microsoft Dataverse Connector in Power Automate
The Common Data Service (current environment) (which is highly likely to be renamed soon) Dataflex (Common Data Service current) Common Data Service (current environment) Microsoft Dataverse connector has Expand Query parameter for Get a record and List records actions which can be used to retrieve the related entity. In one of my previous blog posts, I wrote about how you can use…...
Automatically Create SharePoint Document Location for Dataverse/Dynamics 365 Using Cloud Flow (Part 1 of 6)
This is the first post in a series of Automating SharePoint Integration with Dataverse using Power Automate. You can check out the other posts via these links (Part 2, Part 3, Part 4, Part 5, Part 6) This post will explain how you can automatically create the SharePoint Document Location using the cloud flow in Power Automate when a new row is added to the Dataverse/Dynamics 365 table. … Continue...
How to Set Lookup Fields with Null Value from Dynamic Content in Microsoft Dataverse Connector
In one of my previous blog posts, I wrote about How to Set Lookup Field Value in Microsoft Dataverse Flow Connector. In that blog post, I mentioned that I was not sure how to set a lookup as null either directly or from another record’s lookup field as the output of the step (which can potentially be null). Recently, I discovered a way to do that and I would like to share that with you… Continue Reading...
Automatically Create SharePoint Folder Structure Based on Specific Table in Dataverse Using Cloud Flow (Part 3 of 6)
This is the third post in a series of Automating SharePoint Integration with Dataverse using Power Automate. You can check out the other posts via these links (Part 1, Part 2, Part 4, Part 5, Part 6) In my first post, I have explained how to automatically create the SharePoint Document Location using the cloud flow when a new row is added to the Dataverse/Dynamics 365 table. But if you want to… Continue Reading...
SharePoint Document Upload in Dynamics 365/Microsoft Dataverse with Custom Field (Part 3 of 3)
This is the third post in a series of File field as input and SharePoint as storage. You can check out the other posts via these links (Part 1, Part 2) Customising the document upload dialog box for the purpose of adding an additional field to capture the metadata of the uploaded document is a common ask in the community forums. Now in one of my previous blog posts about How… Continue Reading noreply@blogger.com (Linn...
Mix and Match FetchXML Query with Web API Query Options of Microsoft Dataverse Connector in Power Automate
Recently, Microsoft has added validation in the Flow Checker to show the following warning message to the users if any of the Select Query, Filter Query or Top Count is not specified in the List records action of the Common Data Service (current environment) connector in Power Automate. Update action ‘List Records with Fetch Xml Query’ to use a select query, filter query, or…...
Get Flow Run by Using Dynamics 365/Microsoft Dataverse Record ID as Parameter in Power Automate
There are several ways on how you can access the flow run history in Power Automate. In fact, to make things easier for me, I created a solution and wrote a blog post about how to Access Flow Run History within a Record in Dynamics 365/Microsoft Dataverse (check that out if that is of interest). However, the solution I did is not for everyone especially if there are tons of existing flows in… Continue Reading...
Trigger OnCreate Cloud Flow for Existing Rows (Part 2 of 6)
This is the second post in a series of Automating SharePoint Integration with Dataverse using Power Automate. You can check out the other posts via these links (Part 1, Part 3, Part 4, Part 5, Part 6) In my previous post, I have explained how to automatically create the SharePoint Document Location using the cloud flow when a new row is added to the Dataverse/Dynamics 365 table. But if you… Continue Reading...
Automatically Create SharePoint Document Location for Dataverse/Dynamics 365 Using Cloud Flow (Part 1 of 5)
This post will explain how you can automatically create the SharePoint Document Location using the cloud flow in Power Automate when a new row is added to the Dataverse/Dynamics 365 table. Microsoft Dataverse supports integration with SharePoint Online and with out-of-the-box functionality, the SharePoint folder and the related Document Location data is created on the fly when the… Continue Reading...
Move Attachment from File Field of Microsoft Dataverse to SharePoint in Power Automate (Part 1 of 3)
This is the first post in a series of File field as input and SharePoint as storage. You can check out the other posts via these links (Part 2, Part 3) What is a File field and how you can use it Microsoft has added the File and Image datatypes to Microsoft Dataverse last year which was only available in canvas apps first, and then was later on made available in the model-driven app with… Continue...
The Return of Composite Address Control in Model-driven Apps – Now with Built-in Autocomplete Functionality
Early this year, Microsoft has announced the general availability of address input control as part of geospatial features for canvas apps. But how about model-driven apps? Can we have a similar address input control for model-driven apps too? Capturing addresses is a common business scenario and address lookup functionality is preferred to be used in most of my projects to… Continue Reading noreply@blogger.com (Linn...
Unable to Export Solution from Dataverse/Dynamics 365 with Generic Unexpected Error
When I tried to download the solution in the maker portal, it took really long and finally the following error was shown. Solution “Power Platform Playground” failed to export: An unexpected error occurred. I tried it again in the classic solution explorer, I got the same generic “Unexpected Error” popup and the downloaded log file is not helpful either.
Allow Users Without Delete Privilege on Activity to End Recurring Appointment Series or Convert Single Appointment to Recurring One
This post will explain how you can implement a plug-in that will allow the normal users without prvDeleteActivity (Delete privilege for the Activity table) to end a recurring appointment series, update recurrence information, or convert an existing appointment to a recurring appointment. In most of the Dynamics 365/Power Apps + Dataverse implementations, it is a common practice not… Continue Reading...
Add Two-level up Related Column to a View in Model-driven Apps
In this post, I will explain how you can add a column from the related table (up to two-level up) to the views in model-driven apps. In Dynamics 365 projects or Power Apps (model-driven apps) projects, it is a common requirement to edit the system view to show the columns from the related table. With the out-of-the-box view designer, you can easily add the column from the directly… Continue Reading noreply@blogger.com (Linn...
Handle Base64 and Binary File Content Types in Power Automate
Did you know that there are two types of file or image content type used in the input and output parameters? In this post, you will learn how to handle the different types of file content in the cloud flow action parameters. When working with the input and output parameters for file content, you need to provide a value as Binary data type for most of the input parameters (e.g.
Validating Document Upload in Business Process Flow by Setting Field Requirement Level Conditionally (Part 2 of 3)
This is the second post in a series of File field as input and SharePoint as storage. You can check out the other posts via these links (Part 1, Part 3) Using the File field in Business Process Flow for uploading of documents Sometimes, the new functionalities introduced to the Common Data Service (CDS) platform is not immediately supported in the no-code functionality of the model-driven… Continue Reading...
Use Filter Array instead of Nested List Records to Optimise the Cloud Flow
In this post, I will explain how you can use the Filter Array action to filter the required rows of the output data from the List Records action. When there is a requirement to match the rows from two arrays using a particular property value, you can use the Filter Array action to get the matching object from the array. In the scenario below, you will see how it can be used to get… Continue Reading noreply@blogger.com (Linn...
Retrieve more than 100,000 Dataverse Rows with List Records Action in Cloud Flow Using Skip Token
Have you ever wondered what the Skip Token parameter in the List Records action of Common Data Service (current environment) connector is for? In this post, I will explain how you can retrieve any number of rows, even more than 100,000 rows, by handling paging manually with the Skip Token parameter. By default, the List Records action in Power Automate can retrieve up to 5,000 rows… Continue Reading...
Populate Activity Party Value with JSON Array in Power Automate
In this post, I will explain how you can dynamically populate the Activity Parties or any other array input parameter by switching to input entire array and populating with the JSON array. In cloud flow, when the input parameter of the action is an array data type, the flow designer shows the input parameter in two different modes: Detail inputs… Continue Reading noreply@blogger.com (Linn Zaw Win)’s Article on their...
Perform Bound/Unbound Action with EntityType Parameters in Power Automate
In this post, I will explain how you need to populate the entity (or table) type input parameters for some of the bound/unbound actions in cloud flows. That can be a bit tricky when the input parameters are not simple data types (such as string, boolean, etc.). Some of the entity type parameters are expecting an entity object with column values to be created as a new row… Continue Reading noreply@blogger.com (Linn Zaw...
Dynamically Populate Polymorphic Lookup Value in Power Automate without using Condition Step
In my previous post, I have described how to populate Owner value dynamically in Power Automate. The trick I used in that post only works for the Owner lookup though and not for polymorphic lookups. And the reason why is because if you are using the Dataverse/Common Data Service (current environment) connector, there is only one input parameter for the Owner column unlike for polymorphic… Continue Reading...
Dynamically Populate Owner Value (User or Team) in Power Automate
When building flows in Power Automate, sometimes we need more than just adding a dynamic value for complex scenarios (or at least for complex data types like polymorphic lookups). In this post, you will learn about how to set the value of the Owner field dynamically based on the value of another row’s Owner field (which can be either User or Team). Owner value from Trigger Output In… Continue Reading noreply@blogger.com...
Find ID of SharePoint Document by File Name in Power Automate
Did you know that there are two types of identifiers used in the SharePoint connector to identify an item in a SharePoint list or a SharePoint document? The first one is the “Unique Identifier” (integer type) which is sequentially generated by the system and unique to the list or library (e.g. 13). The other one is the “File Identifier” (string type) which is the “folder + file...
Mix and Match FetchXML Query with Web API Query Options of CDS Connector in Power Automate
Recently, Microsoft has added validation in the Flow Checker to show the following warning message to the users if any of the Select Query, Filter Query or Top Count is not specified in the List records action of the Common Data Service (current environment) connector in Power Automate. Update action ‘List Records with Fetch Xml Query’ to use a select query, filter query, or…...
Time Picker in Power Apps Canvas App and Daylight Saving
Date/Time picker is one of the fundamental controls which is not available in Power Apps canvas app yet. The Power Apps idea of adding “Time” picker on the Date picker control has been under review since 2018 and the idea of Time Picker control has been planned since 2017. For those who are building canvas apps for Dynamics 365 / Common Data Service would get the requirement to… Continue Reading...
SharePoint Document Upload in Dynamics 365/CDS with Custom Field (Part 3 of 3)
This is the third post in a three-part series of File field as input and SharePoint as storage. You can check out the other posts via these links (Part 1, Part 2) Customising the document upload dialog box for the purpose of adding an additional field to capture the metadata of the uploaded document is a common ask in the community forums. Now in one of my previous blog posts … Continue Reading noreply@blogger.com (Linn Zaw...
Move Attachment from File Field of CDS to SharePoint in Power Automate (Part 1 of 2)
This is the first post in a two-part series of File field as input and SharePoint as storage. You can check out the second post via this link.What is a File field and how you can use it Microsoft has added the File and Image datatypes to Common Data Service last year which was only available in canvas apps first, and then was later on made available in the model-driven app with 2020 Release…...
Validating Document Upload in Business Process Flow by Setting Field Requirement Level Conditionally (Part 2 of 2)
This is the second post in a two-part series of File field as input and SharePoint as storage. You can check out the first post via this link.Using the File field in Business Process Flow for uploading of documents Sometimes, the new functionalities introduced to the Common Data Service (CDS) platform is not immediately supported in the no-code functionality of the model-driven apps and… Continue Reading noreply@blogger.com...
Various Ways to Disable/Skip/Comment out Flow Steps when Testing in Power Automate
Sometimes when we are debugging flows, we want some of the steps to be disabled/skipped and ignored by the Power Automate engine so that those actions are not triggered while we are still working on the other parts of the flow. But currently, there is no way in Power Automate to disable the steps for testing/debugging scenarios (yet) even though the Power Automate team has been working… Continue Reading noreply@blogger.com (Linn...
Get Flow Run by Using Dynamics 365/CDS Record ID as Parameter in Power Automate
There are several ways on how you can access the flow run history in Power Automate. In fact, to make things easier for me, I created a solution and wrote a blog post about how to Access Flow Run History within a Record in Dynamics 365/CDS (check that out if that is of interest). However, the solution I did is not for everyone especially if there are tons of existing flows in the system… Continue Reading...
Get JSON Output of Steps with Status Reason 200 in Power Automate
The JSON output in the run history of the List records action step from the Common Data Service (current environment) connector is useful for troubleshooting purposes or getting the sample data for Parse JSON action. It is also useful when you need to see the attributes which are not listed in ‘Dynamics content’ pane (e.g. OData.Community.Display.V1.FormattedValue properties, or...
Get Output Data from Expand Query of CDS (current environment) Connector in Power Automate
The Common Data Service (current environment) connector (which is highly likely to be renamed soon) Dataflex (Common Data Service current) connector has Expand Query parameter for Get a record and List records actions which can be used to retrieve the related entity. In one of my previous blog posts, I wrote about how you can use Expand Query to retrieve related data. The example I… Continue Reading...
How to Set Lookup Fields with Null Value from Dynamic Content in CDS (current environment) Connector
In one of my previous blog posts, I wrote about How to Set Lookup Field Value in Common Data Service (current environment) Flow Connector. In that blog post, I mentioned that I was not sure how to set a lookup as null either directly or from another record’s lookup field as the output of the step (which can potentially be null). Recently, I discovered a way to do that and I would… Continue Reading noreply@blogger.com...
Get the Lookup Display Name and Option Set Value Label in a Single Query Using a CDS (Current Environment) Connector FormattedValue Property
One of the limitations in using Common Data Service (current environment) connecter in Power Automate comparing to the classic workflow WAS the inability to get the display name of the lookup value or the label of the option set value in one simple query. However, this is actually not the limitation of the platform itself. It seems that the CDS (current environment) actions did not use… Continue Reading...
Minimum Privileges Required to Log in to Model-driven Apps in Dynamics 365/CDS
One of the security best practices in Dynamics 365 is to use the base security role as a baseline and apply that role to all Users. The base security role will include all the common/basic permissions that are required to have access to the system (you can read more details in Tip #2 of Power Platform / Dynamics CRM Tip of the Day). The advantage of using the base security role is… Continue Reading...
Script Errors Encountered after Field Service Upgrade to 8.x
In one of my projects, I suddenly encountered script errors after upgrading the Field Service solution from version 7.x to 8.x (the latest version). When loading the Quote and Product line item forms, the system shows the following error message: Script Error One of the scripts for this record has caused an error. For more details, download the log file. … Continue Reading noreply@blogger.com (Linn Zaw Win)’s Article on...
Access Flow Run History within a Record in Dynamics 365/CDS
As recommended by Microsoft, I have been creating automated flows instead of background workflows for a while now (obedient me!). But not being able to see the list of Background Processes related to the record is one of the things that I miss from the classic background workflows (especially when I am having an issue 🐛 with a particular record). Although we no longer have the… Continue Reading...
Send Email to Unresolved Recipients in Dynamics 365 using Power Automate
There are times when you need to send an email to unresolved recipients in Dynamics 365. An unresolved recipient is an email address which is not stored in the system (i.e. not stored in contact, user, queue, etc.). Dynamics 365 has an option to allow messages with unresolved email recipients to be sent from the system. This option can be used in different scenarios such as sending to a… Continue Reading noreply@blogger.com...
How to Add Metadata to SharePoint Document Subgrid in Dynamics 365
As mentioned in the Dynamics CRM Tip Of The Day Tip #1185, you can customise the SharePoint document subgrid for server-side integration. At the time of publishing that post, the view was not customisable via solution explorer yet but in this forum answer, the Document Associated Grid of the SharePoint Document entity can now be editable via solution explorer. These are the list of… Continue Reading...
Build Efficient Flows Using Filter Expression in CDS (current environment) Trigger
One of the key best practices for creating an efficient automated flow in Power Automate (Dynamics 365 or Common Data Service) is to properly set the options on the trigger of the flow to minimise unnecessary triggering and reduce execution time. As specified in a guide to building enterprise-ready flows, you should always set attribute filters unless you are interested in any change to… Continue Reading...
Import Data Behaviour for Lookup Fields in Dynamics 365 (CDS)
There are several ways to import the data into Dynamics 365 or Common Data Service and one of them is using out-of-the-box Data Import Wizard. When the Import Data functionality is used to create the records, the system handles the lookup fields differently from the other types of data. If the lookup field requirement option is Business Required (Mandatory), the system resolves the lookup… Continue Reading...