Enable SharePoint Online integration Dynamics 365 | Power Platform Admin Center

In this post, I will highlight on how you can enable SharePoint Online Document Integration with Dynamics 365 CRM and how these records are structured in SharePoint as well as Dynamics CRM.

Hope this post covers it for you to get started with Dynamics 365 SharePoint Online Integration! 😊

Pre-requisites

Here are the pre-requisites you need to make sure you can enable SharePoint Online integration with Dynamics 365 CE/CRM.

  1. With Dynamics 365 Online, you’ll also need SharePoint Online plan as well which is available with M365/O365 Plans. Example: E3

  2. Also, make sure you are Dynamics 365 Admin as well as SharePoint Admin as well. In case you happen to the be Global Administrator, even better! 😊

Before enabling SharePoint Integration

Before we enable SharePoint Integration, notice that Documents is not shown in related records under entities like Accounts, for example.



Power Platform Admin Center

You can visit Power Platform Admin Center (https://admin.powerplatform.microsoft.com/environments) to enable SharePoint Integration

  1. Navigate to Power Platform Admin Center (https://admin.powerplatform.microsoft.com/environments) and then to the environment with which you want to enable the SharePoint Online integration with –
    Then, go the to Settings of the Organization –

  2. Under the Integration section, navigate to Document management settings

  3. It’ll take you to the old Document Management Settings in Dynamics 365 CRM. Here, you’ll be able to select the Enable Server-Based SharePoint Integration

  4. The next dialog box will walk you through the steps to enable the SharePoint Integration with your Site. Click Next.

  5. Now, you’ll be asked if you want to enable for Online or On-premise. In this example, we are looking at Online, hence, Online will be selected and you click Next.

  6. Further, you’ll be asked what Site should the integration be enabled on.

  7. It should be the SharePoint Site you want to enable this to, so you can pick it from the SharePoint site itself. Copy the selected URL from your respected SP Site.


    And paste it in the box where URL is asked. Then click Next as shown below.

  8. Final step is to click Finish post the Site is found to be Valid.


  9. At this point, Documents will be visible on entities.

  10. But, if you navigate and try to enter Documents, you’ll see the error message saying that Site is missing

    This completed the first step of the process. Next step is to enable the entities for SharePoint integration of Documents.

Enable Entities for SharePoint Integration

In this section, once we have enable the Dynamics 365 environment for SharePoint integration, we’ll now enable the entities which we want the Document Integration to be enabled on –

  1. Now, you’ll need to enable the entities for Document Management


  2. In this, you have to make enter the URL of the SharePoint Site where you want the Document Library to reside. I’m entering the main SharePoint URL itself and we’ll see where this ends up.
    In this, make sure you select the Entities which you want to enable for Document Management.
    Most of common Business Entities are pre-selected, you only need to paste the URL of the Site location and you are good to click on Next.

  3. Next, it’ll ask the structure of the folders that should be created in the SharePoint.
    To understand Based on Entity, you can check this – https://d365demystified.com/2018/12/17/based-on-entity-folder-structure-in-d365-sharepoint-online-integration-in-d365/

  4. Once you click Next based on your selection, you’ll simply be prompted where the Document Locations are being created.
    You just need to click OK.

  5. Further, it’ll process the entities which were initially selected in #2 above.

  6. In a few moments, this will be completed.
    You can simply click finish.

  7. Once done, you can now check that the error in Account’s Document section is gone and you’ll see that the Documents grid is ready for Documents to be uploaded.

  8. And here’s the SharePoint Folder Structure created in SharePoint.


  9. When you navigate and even if you open the grid on the Dynamics 365 record, the folder is created in SharePoint even if you don’t upload anything.

  10. And for example, you upload a sample Document on the record

  11. It’ll appear in the Documents tab here.

  12. And also on the SharePoint library which we just saw

    Easy!!

SharePoint Site Structure in Dynamics 365

If you are further curious on what happens in Dynamics 365 and which kind of records are created, here you go –

  1. The first record to be created in a high-level is SharePoint Site.
    Under this, a Document Location record is created.

  2. And in this Document Location record, a Default Document Location is created which will house the other records

  3. And in this Document Location record itself (if you open the one marked in the #2 above)
    A child Document Location record is created [And this is created when you open the Document tab on the entity record itself]
    So, go to the Document Locations in related in the Documents on Default Site 1 itself

  4. And these are the records under the Child Document Location records.

    So this is what happens on a very high-level. 😊

Hope this was helpful! Here are some more Dynamics 365 posts which you might be interested in –

  1. Dynamics 365 Storage Utilization | Dataverse Storage | Power Platform Admin Center
  2. Use Hierarchy in Roll Up Fields in Dynamics 365 CRM
  3. Filter records in a View owned by a Team you are a member of | Dynamics 365 CRM
  4. Get GUID of the current View in Dynamics 365 CRM JS from ribbon button | Ribbon Workbench
  5. Dynamics 365 App For Outlook missing on SiteMap in CRM? Use shortcut link [Quick Tip]
  6. Import lookup referencing records together in Dynamics 365 CRM | [Linking related entity data during Excel Import]
  7. Mailbox Alerts Hide/Show behavior in Dynamics 365 CRM
  8. Excel Importing Notes (Annotation) entity in Dynamics 365 CRM
  9. Enable/Disable the need to Approve Email for Mailboxes in Dynamics 365 CRM CE
  10. Call Azure Function from Dynamics 365 CRM using Webhooks
  11. Show Ribbon button only on record selection in Dynamics CRM
  12. Accessing multiple occurrences of a field in Business Process Flow using JS in D365 CRM

Thank you!!

Advertisement

Call Flow from Webhooks in Dynamics 365 CRM | Power Automate

In case you are wondering if there are other ways to call a Flow apart from just Dataverse connectors, well – There are ways! 😊

Here’s how you can use Webhooks registered on Dynamics 365 CRM to call a Flow in Power Automate using HTTP Request trigger

Pre-Requisites

Given that you already have Admin Access to create Flows with HTTP Request Triggers, you’ll need to have Plugin Registration Tool in case you are not familiar – Download Plugin Registration Tool for Dynamics 365 CRM usingΒ PowerShell

Initiate a Flow

Here’s how you start building your Flow –

  1. You must select the HTTP Trigger when you start a new flow. This will be your Flow trigger.

  2. Now, in order to be able to get the URL of the HTTP Trigger which you’ll need, you’ll need to save the Flow first.
    And for that, Flow needs to have more than 1 step. So just go ahead and add a variable, maybe. 😊

  3. Once you save the Flow, the URL will be generated which you can copy

  4. Copy this URL and paste it in the Notepad. We’ll come to it later.
    It should look like this –

    So we’ll come to this later. Let’s keep this handy in clipboard since you’ve copied it anyway and let’s move towards registering the Webhook itself.

Register Webhook in Dynamics 365 CRM

Given that you have Plugin Registration Tool and you are logged in, you can proceed with registering a Webhook in the environment –

  1. In the menu, select Register a Webhook option.

  2. Now, you can start by giving it a name.
    Then, in Endpoint URL – copy only till the work invoke
    https://prod-131.westus.logic.azure.com:443/workflows/6092c774224e498ebe413f3d7c05a45e/triggers/manual/paths/invoke?api-version=2016-06-01&sp=%2Ftriggers%2Fmanual%2Frun&sv=1.0&sig=gvfm52Mpnhsz4Ew4ufRllNM_VhfC6a-GkCpM7AigPU0

    Also, select the Authentication as HttpQueryString

  3. Now, coming the next part, you can start add properties to this –
    Green are the Properties, Pink are the Values

    https://prod-131.westus.logic.azure.com:443/workflows/6092c774224e498ebe413f3d7c05a45e/triggers/manual/paths/invoke?api-version=2016-06-01&sp=%2Ftriggers%2Fmanual%2Frun&sv=1.0&sig=gvfm52Mpnhsz4Ew4ufRllNM_VhfC6a-GkCpM7AigPU0

    Also, in case you are wondering what does the %2F mean – It’s the HTML encoding for a slash symbol “/
    Ref Link: https://www.w3schools.com/tags/ref_urlencode.ASP

    And, the properties should look like below –


  4. Now, you can go ahead and add a Step just like you would do in a Plugin assembly


    And then, for example, register a step on Associate. It could be any message.

  5. And, when you Associate a record, example – Assigning a security role to a User –

  6. The Webhook will call the HTTP Request Flow


    And if you open the Flow, you can expand the first step and see the Detailed outputs






  7. You can copy the above Outputs and use this to generate Schema for the HTTP Trigger so that you can use it further in the Flow


    And this is how it will be generated

Hope this helps!

Here are some Power Automate posts you want to check out –

  1. Showing Sandbox or Non Production Apps in Power App mobile app
  2. Create a Power Apps Per User Plan Trial | Dataverse environment
  3. Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
  4. Co-presence in Power Automate | Multiple users working on a Flow
  5. Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
  6. Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
  7. Call a Flow from Canvas Power App and get back response | Power Platform\
  8. FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
  9. Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
  10. Asynchronous HTTP Response from a Flow | Power Automate
  11. Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
  12. Converting JSON to XML and XML to JSON in a Flow | Power Automate

Thank you!

Pinning Records in Dynamics 365 CRM in Unified Interface [Quick Tip]

A small but super useful feature is to be able to access pinned records which you frequently visit / need to visit.

Pinning Records

Here’s how you pin records in Dynamics 365 CRM –

  1. In your left-hand-side of the navigation pane, you’ll see Recents and Pinned section.
    Right away, no records are pinned. You can pin records from Recent items only at this point.

  2. If you expand the Recents section, you can hover over the records to find the pin appear on the records which you want to pin.

  3. Once you pin them, they’ll appear in your Pinned area. Since you Recent records would change over time as you continue to access different records.

  4. In case you want to remove this, you can also unpin by clicking on the unpin icon as shown below

  5. Good thing is that pinned records are available all other Apps as well.
    So you could be in any App and you’ll retain all the Pinned items

Hope this was helpful! Here are some more Dynamics 365 posts which you might be interested in –

  1. Use Hierarchy in Roll Up Fields in Dynamics 365 CRM
  2. Filter records in a View owned by a Team you are a member of | Dynamics 365 CRM
  3. Get GUID of the current View in Dynamics 365 CRM JS from ribbon button | Ribbon Workbench
  4. Dynamics 365 App For Outlook missing on SiteMap in CRM? Use shortcut link [Quick Tip]
  5. Import lookup referencing records together in Dynamics 365 CRM | [Linking related entity data during Excel Import]
  6. Mailbox Alerts Hide/Show behavior in Dynamics 365 CRM
  7. Excel Importing Notes (Annotation) entity in Dynamics 365 CRM
  8. Enable/Disable the need to Approve Email for Mailboxes in Dynamics 365 CRM CE
  9. Call Azure Function from Dynamics 365 CRM using Webhooks
  10. Show Ribbon button only on record selection in Dynamics CRM
  11. Accessing multiple occurrences of a field in Business Process Flow using JS in D365 CRM

Thank you!!

Download Plugin Registration Tool for Dynamics 365 CRM using PowerShell

If you are new to plugin development, you must’ve learnt by now that you’ll need to download and install a Plugin Registration Tool in order to register your plugin with the Dynamics 365 environment you are working on.

In case you are on your own and someone hasn’t given you the zip file already, here’s how you can start from scratch. 😊

Download Plugin Registration Tool using PowerShell

Here’s how you start from the very beginning.

  1. If you do a quick Google Search, you might find someone must’ve already uploaded a Plugin Registration Tool somewhere, but in case you want to get it from Microsoft’s official website, here’s the link to Microsoft Docs – https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/download-tools-nuget?view=op-9-1&viewFallbackFrom=op-9-1%3FWT.mc_id%3DDX-MVP-5003911
    Then, you can directly navigate to the Plugin Registration Tool segment by clicking on the highlighted link below


  2. In Plugin Registration Tool, you can simply click on the Download Package button


    This file Nuget file will be downloaded to your machine –

  3. Now, open PowerShell in Admin mode –

  4. Now, write the below code in PowerShell [Make sure you are pointing to the directory where you want to install the Nuget.exe]
    [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 $sourceNugetExe = "https://dist.nuget.org/win-x86-commandline/latest/nuget.exe" $targetNugetExe = ".\nuget.exe" Remove-Item .\Tools -Force -Recurse -ErrorAction Ignore Invoke-WebRequest $sourceNugetExe -OutFile $targetNugetExe Set-Alias nuget $targetNugetExe -Scope Global -Verbose

    It’ll look like this when you type and press Enter, after a few moments when it’s completed downloading, you’ll be in the below state –

  5. Now, Microsoft Docs article above lists the PS Script to download all the Tools, but from that, if you want to only Download Plugin Registration Tool for now, that’s fine! You can just write the below PS Script and leave the rest –

    PS Script for Plugin Registration Tool only –
    ## ##Download Plugin Registration Tool ## ./nuget install Microsoft.CrmSdk.XrmTooling.PluginRegistrationTool -O .\Tools md .\Tools\PluginRegistration $prtFolder = Get-ChildItem ./Tools | Where-Object {$_.Name -match 'Microsoft.CrmSdk.XrmTooling.PluginRegistrationTool.'} move .\Tools\$prtFolder\tools\*.* .\Tools\PluginRegistration Remove-Item .\Tools\$prtFolder -Force -Recurse



    And when you press enter, it’ll setup the same and this will be your completed state –

  6. And you are done! Plugin Registration Tool has been downloaded
    And since we only Downloaded the Plugin Registration Tool and nothing else, only Plugin Registration Tool folder will be seen

  7. And here’s your Plugin Registration Tool


Hope this was helpful! Here are some more Dynamics 365 posts which you might be interested in –

  1. Dynamics 365 Storage Utilization | Dataverse Storage | Power Platform AdminΒ Center
  2. Use Hierarchy in Roll Up Fields in Dynamics 365Β CRM
  3. Filter records in a View owned by a Team you are a member of | Dynamics 365Β CRM
  4. Get GUID of the current View in Dynamics 365 CRM JS from ribbon button | RibbonΒ Workbench
  5. Dynamics 365 App For Outlook missing on SiteMap in CRM? Use shortcut link [QuickΒ Tip]
  6. Import lookup referencing records together in Dynamics 365 CRM | [Linking related entity data during ExcelΒ Import]
  7. Mailbox Alerts Hide/Show behavior in Dynamics 365Β CRM
  8. Excel Importing Notes (Annotation) entity in Dynamics 365Β CRM
  9. Enable/Disable the need to Approve Email for Mailboxes in Dynamics 365 CRMΒ CE
  10. Call Azure Function from Dynamics 365 CRM usingΒ Webhooks
  11. Show Ribbon button only on record selection in DynamicsΒ CRM
  12. Accessing multiple occurrences of a field in Business Process Flow using JS in D365Β CRM

Thank you!!

Dynamics 365 Storage Utilization | Dataverse Storage | Power Platform Admin Center

If you are new to using Dynamics 365 and if you are looking to check how much storage is being utilized in Dynamics 365, here’s how you can check it –

Power Platform Admin Center

Here’s how you check the storage utilization of your Dynamics 365 / Dataverse instances in your tenant –

  1. Provided you have the right access, navigate to the Power Platform Admin Center (https://admin.powerplatform.microsoft.com/environments)
    Now, expand the Resources section which would be collapsed as pointed in the screenshot below.

  2. Under Resources, you’ll find Capacity section under the same.

  3. When in Capacity, you’ll see Dataverse section. Although, you’ll still find the summary but not in detailed numbers.


  4. In Dataverse section, you’ll see the list of you Dataverse / Dynamics 365 CRM instances listed and having a summary of their current storage utilization. You can click on the graph icon to further drill down into the details.

  5. Let’s say – I’m into CFT158 environment, so – I’ll see all the details of that environment.
    Also, notice the hamburger menu on the top left.

  6. Clicking on the hamburger menu, you’ll see some options which you can use to view/get this data.
    One important one is to get the details of all the tables (Since only top 10 tables are listed in the view you see)

  7. Let’s say you clicked on Downloaded all tables as shown in the screenshot above, a CSV file will be exported on your system and will contain all the tables’ storage utilization and not just top 10 tables.

  8. Also, here’s a Microsoft Docs link on detailed explanation of how you can utilize the Storage details – https://docs.microsoft.com/en-gb/power-platform/admin/legacy-capacity-storage#environment-capacity-analytics?WT.mc_id=DX-MVP-5003911

Hope this was helpful! Here are some more Dynamics 365 posts which you might be interested in –

  1. Use Hierarchy in Roll Up Fields in Dynamics 365 CRM
  2. Filter records in a View owned by a Team you are a member of | Dynamics 365 CRM
  3. Get GUID of the current View in Dynamics 365 CRM JS from ribbon button | Ribbon Workbench
  4. Dynamics 365 App For Outlook missing on SiteMap in CRM? Use shortcut link [Quick Tip]
  5. Import lookup referencing records together in Dynamics 365 CRM | [Linking related entity data during Excel Import]
  6. Mailbox Alerts Hide/Show behavior in Dynamics 365 CRM
  7. Excel Importing Notes (Annotation) entity in Dynamics 365 CRM
  8. Enable/Disable the need to Approve Email for Mailboxes in Dynamics 365 CRM CE
  9. Call Azure Function from Dynamics 365 CRM using Webhooks
  10. Show Ribbon button only on record selection in Dynamics CRM
  11. Accessing multiple occurrences of a field in Business Process Flow using JS in D365 CRM

Thank you!!

Connections used in which Flows or Power Apps | Power Platform Tip

If you are wondering that it would be easy to find which all Flows are using a certain Connection in Power Automate, you are right – it is easy. 😊

Here’s a quick tip!

Power Automate Admin Center

You can navigate to the Power Automate portal i.e. <region>.flow.microsoft.com.

  1. In this example, this is my Power Automate (which is https://[region].flow.microsoft.com/en-us/).
    In that, I’ll expand Data from the left hand menu and go to Connections.


  2. In Connections, you’ll see redundant Connections based on how you might have created them.

  3. Select any one of them, click on the three dots i.e. the Ellipses and look for Details.


  4. In Details, you’ll see the section called as Flows using this connection. Meaning, this will show that the particular Connections is used in which Flows.

  5. In Flows using this connection, you’ll see the list of all Flows.


  6. Opening any one will only open all the Flows and not do anything else. Won’t navigate to the selected Flow.


  7. Same is also true for Power Apps as well.


  8. At this point, the naming/renaming connections is not possible but could be available soon.

Hope this helps!

Here are some Power Automate posts you want to check out –

  1. Showing Sandbox or Non Production Apps in Power App mobile app
  2. Create a Power Apps Per User Plan Trial | Dataverse environment
  3. Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
  4. Co-presence in Power Automate | Multiple users working on a Flow
  5. Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
  6. Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
  7. Call a Flow from Canvas Power App and get back response | Power Platform\
  8. FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
  9. Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
  10. Asynchronous HTTP Response from a Flow | Power Automate
  11. Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
  12. Converting JSON to XML and XML to JSON in a Flow | Power Automate

Thank you!

Follow up message in Teams using Power Automate for Teams app

Now that Power Automate is in GA in Teams, there are a ton of automations you can perform and quite a few of them already ready to be consumed right within the templates itself without you having to do anything at all.

One such important Flow is setting Follow up on messages! Let’s look at how we can find and use this

Power Automate in Teams

Power Automate is now in Teams as well. Here’s how you can get it –

  1. You can go the Apps in Teams. Then, look for Power Automate.

  2. Now, you’ll see this populate template called as Follow up on a message which is already created completely for you.


  3. Once you select this, you’ll just need to confirm. I’ll just call it Follow up on a message. Then, I’ll simply click on Create flow.

  4. Once you click on Create, you’ll see a confirmation message that the Flow has been created.

  5. You’ll see it turned on in your Home in Power Automate.

  6. Now, once this is setup, you’ll see a Bot on the Chat list in Teams.

  7. And it will show you that the Flow is ready to run.


Following up on a message in Teams

So here’s how it does –

  1. Let’s say I got a message from a colleague that he’ll get back to me in 5 mins.

  2. Now, in case I forget, it’ll be gone and I might remember this by myself much later. Here’s where I can add a follow up to this. So, I’ll click on the three dots (ellipses) and go to More Actions and then see the Flow I created.

  3. Now, it’ll ask me some details as to when I want to follow up and what should show up.
    So, I’ll enter the Date & Time of when I want to be reminded and what the reminder should say.

  4. And, at the given time, the Flow Bot will pop this message in it’s own chat window.
    I can go to the message.


  5. And it’ll simply take me to the message. On the phone app, it subtly glows for a brief moment (Perhaps this could some to Teams in a more prominent way)


Hope this helps!

Here are some Power Automate posts you want to check out –

  1. Showing Sandbox or Non Production Apps in Power App mobile app
  2. Create a Power Apps Per User Plan Trial | Dataverse environment
  3. Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
  4. Co-presence in Power Automate | Multiple users working on a Flow
  5. Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
  6. Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
  7. Call a Flow from Canvas Power App and get back response | Power Platform\
  8. FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
  9. Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
  10. Asynchronous HTTP Response from a Flow | Power Automate
  11. Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
  12. Converting JSON to XML and XML to JSON in a Flow | Power Automate

Thank you!

Comments in Power Platform [Preview] | Power Automate example

Here’s a new feature across Power Platform stack i.e. Power Apps / Power Virtual Agents and Power Automate

Comments

Let’s consider an example of a Flow / Power Automate for the Comments

  1. In a Cloud Flow, now you’ll see a Comments (preview) show up.

  2. When you click on it, Comments pane will open up letting you add Comments to the Flow.

  3. And just like in Word, you’ll be able to enter comments for the Flow. These comments are added pertaining to the selected Flow Step or the first Flow Step by default.
    Click on the send button to add the comment.

  4. Now, once a comment is added, a counter/badge of count of comments will appear on the Step the comment is tied to.

  5. As you proceed, multiple users can add their comments to different steps. (Ideally, since I added 2 comments to the second step, both should be highlighted. This could be in preview and in the works). I’ll update this space again as I have more info

  6. Similarly, a thread looks like the one highlighted on the right and if you notice, the Flow Step too will lit up a little to denote which step the comment thread belongs to.
    Also, a comment thread is treated as count of 1.

  7. For each thread, you have the below options per thread/comment.

  8. And if you Resolve a comment/thread, notice that the counter from the Flow Step is discounted/removed and the comment thread is marked with Resolved tag on the top.

    Also, the step it belongs to is highlighted a little and is slightly difficult to identify right away
    Perhaps this behavior could be changed in the future once in GA.


  9. Once a thread is Resolved, it could be Reopened or Deleted as the icons suggest.

Hope this helps!

Here are some Power Automate posts you want to check out –

  1. Showing Sandbox or Non Production Apps in Power App mobile app
  2. Create a Power Apps Per User Plan Trial | Dataverse environment
  3. Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
  4. Co-presence in Power Automate | Multiple users working on a Flow
  5. Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
  6. Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
  7. Call a Flow from Canvas Power App and get back response | Power Platform\
  8. FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
  9. Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
  10. Asynchronous HTTP Response from a Flow | Power Automate
  11. Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
  12. Converting JSON to XML and XML to JSON in a Flow | Power Automate

Thank you!

Range function in Power Automate | Quick Tip

Here’s a pretty simple look at how you can create an Array of numbers from a Start of the number to the End number and an Array of the range will be created

Example Variable

I’m just creating a sample variable to hold the array I’m creating –

  1. Initialize a variable and it should look like below

Range function in Power Automate

Now, if you look at the Dynamic Content section, you’ll be able to find the range function. Let’s see how –

  1. In Dynamic Context, search for range function

  2. In the range function, you first need to input the Start number of what the array should start.
    In this example, I’m starting from number 4

  3. And once I put a comma, I’ll mention how many items in the array from the number 4 should be contained in the array (including 4 as well)
    So, I enter 12. This doesn’t mean the ending number of the Array should be 12, it means put 12 items.

  4. And then just click OK to set the Array in the variable. Then, save and Run.

  5. Now, when you Run the Flow, you’ll see the Output as below.
    Starting from number 4, there are 12 items and hence, ending at 15

Hope this was helpful!

Here are some more Power Automate / Flow posts you might want to check out –

  1. Retrieve Metadata of Global OptionSets from Dynamics 365 in Power Automate | HTTP with Azure AD action
  2. Primary Key of Activity type entity in a Dataverse connector in Power Automate | Quick Tip
  3. Split On in Power Automate in SharePoint trigger for Item updates
  4. Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
  5. Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
  6. Invalid XML issue in Dataverse connector for List Rows action | Fetch XML Query | Power Automate
  7. FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
  8. Invalid type. Expected Integer but got Number error in Parse JSON – Error at runtime after generating Schema | Power Automate
  9. Asynchronous HTTP Response from a Flow | Power Automate
  10. Setting Lookup in a Flow CDS Connector: Classic vs. Current Environment connector | Power Automate Quick Tip

Thank you!

Block Connector access in Power Platform Admin Center | Power Apps & Power Automate

You can define policies in Power Platform Admin to restrict the use of certain connectors, both – prebuilt and custom connectors in the Power Platform.

Setting DLP Policy for Connectors – Blocking connectors

You’ll need to go to Power Platform Admin Center (https://admin.powerplatform.microsoft.com/)


  1. In Power Platform Admin Center, you’ll need to expand the section called as Policies and you’ll find the option called as Data Policies

  2. In this, you can create Policies for the Connectors which are used in Power Automate / Power Apps

  3. Once you start to create your Policy, give it a suitable name –


  4. Next, I’ll get a list all uncategorized Connectors which I can either choose to select and start Blocking them or send them to Business category.


  5. Let’s say you want to set a policy to restrict certain Actions on the connector called as Power Automate Admins connector. I want to now move this connector to Blocked category.
    So, I find the connector, select and and click on Block as shown below.


  6. Now, I’ll see this connector in the Blocked section.


  7. For now, I’ll ignore the Custom Connectors because I don’t have any for now.

  8. And then, proceed further to define the Scope of this policy i.e. on Environment level.
    For this example, Add all environments is selected since I want to have this for all environments and not selective ones. Quite self-explanatory.

  9. Finally, I’ll Create this Policy.

  10. And you’ll see your Policy created like this –

Policy Usage

Now, let’s review how this policy will work.

  1. Now, in a Flow, I’ll select the Connector for which we’ve set the Policy for. The policy doesn’t hide anything, it let’s you select it first.


  2. And if you select any Action from the Flow, the Flow Checker indicator will light up indicating an error.

  3. And if you expand, it’ll state that the connector is not allowed to be used.
    This won’t allow you to save the flow, forcing you to revoke the step you have performed.



Blocking selective Actions in Connectors

Given you don’t want to Block the whole connector but want to only restrict selective Actions in a connector, here’s what you can do –

  1. While we are tweaking our existing policy, let me take a chance to also show you that you can edit the Policy from the List. Select it, and then click on Edit Policy.

  2. Now, let’s assume our Connector not blocked in the first place and exists in either of the categories i.e. Business or Non-Business.
    Find the connector. Then find the three dots and expand the menu to further show Configure connector (preview) and then select Connector actions

    Remember, this is in Preview and we’ll need to wait to use it for Production once in GA.
  3. Now, you can select what all Actions should be allowed and what all shouldn’t be in order to restrict any unwanted operations configured by other Admins.
    In this scenario, let’s just allow ‘Disable Flow as Admin‘ action and restrict all other ones.

  4. Now, the allowed one will not have any issues.


  5. And the ones we have not allowed, will show the error in the Flow Checker.


Here are some Power Automate posts you want to check out –

  1. Showing Sandbox or Non Production Apps in Power App mobileΒ app
  2. Create a Power Apps Per User Plan Trial | DataverseΒ environment
  3. Install On-Premise Gateway from Power Automate or Power Apps | PowerΒ Platform
  4. Co-presence in Power Automate | Multiple users working on aΒ Flow
  5. Search Rows (preview) Action in Dataverse connector in a Flow | PowerΒ Automate
  6. Suppress Workflow Header Information while sending back HTTP Response in a Flow | PowerΒ Automate
  7. Call a Flow from Canvas Power App and get back response | PowerΒ Platform\
  8. FetchXML Aggregation in a Flow using CDS (Current Environment) connector | PowerΒ Automate
  9. Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE)Β connector
  10. Asynchronous HTTP Response from a Flow | PowerΒ Automate
  11. Validate JSON Schema for HTTP Request trigger in a Flow and send Response | PowerΒ Automate
  12. Converting JSON to XML and XML to JSON in a Flow | PowerΒ Automate

Thank you!