Skip to main content

Power Automate Get absolute Sharepoint URL from document location

Document Locations

If you enable Sharepoint document integration in your model driven apps, you can define for which entities the possibility to upload documents to sharepoint shall be offered and you can define a folder structure.

Possible folder structures can either be based on account or contact, which means if you create child items (e.g. opportunities, activities, ...) sub folders are created below.

If an entity is enabled for document management a "Files" tab is added to the form of your model driven app and as soon as you click on that tab a folder is automatically generated on Sharepoint.

Once the folder has been created you have options to create new or upload existing file or to open the document location (folder) on Sharepoint:

What happens behind the scenes is, as soon as you click on the files tab your model driven app checks, weither a "document location" for this item already exists, or not.

The document location is an own entity in CDS, that acts as the connecting part between CRM and Sharepoint:

It stores information like the regarding record, the relative url (= folder) and the parent document location (= parent folder):

So if you have e.g. a structure based on account, you would have multiple document locations, like:
parent site > account  > account name _ guid > opportunity > topic _ guid ... and all of them just store the relative url.

Identify absolute URL

But what happens under the hood if you click on "Open document location"? How does Dynamics generate the absolute URL of the underlying Sharepoint location?

For that purpose an own Web API function called RetrieveAbsoluteAndSiteCollectionUrl exists. This function returns the absolute Sharepoint url and the url of the site collection.

Power Automate - Get absolute Sharepoint URL

Some time ago I blogged about how to upload e-mail attachments from CRM to Sharepoint using Power Automate / Flow:

What I did not describe back then was, how to setup the necessary document locations in CRM or identify the absolute URL of existing sharepoint locations, e.g. if you have to move certain folders on Sharepoint.

This is something I've been working on the last days and it looks like that:

I check using a "List records action" weither a document location already exists for an opportunity, or not:

If the folder exists, I invoke an http request and call the web api function RetrieveAbsoluteAndSiteCollectionUrl to get the absolute URL of the underlying Sharepoint folder, like that:

<CRM URL>/api/data/v9.1/sharepointdocumentlocations(<GUID of documentlocation>)/Microsoft.Dynamics.CRM.RetrieveAbsoluteAndSiteCollectionUrl()

Then I parse the JSON and get the absolute URL and site collection URL:

Based on that information I can work out the url of the sharepoint site, the document library or the folder, depending on what input your sharepoint action needs (e.g. create file, move folder, ...):


Post a Comment

Popular posts from this blog

Working with Optionset lables in Power Automate

Connector Types Power Automate currently offers 3 different connectors, to connect Power Automate with your Dynamics 365 instance: Dynamics 365 Common Data Service Common Data Service (current environment) Today we will look on ways how to retrieve option set labels via the different connectors, for our sample accounts: Dynamics 365 This connector should not be used any more , since in April 2019 it has been announced as being deprecated. With the Dynamics 365 connector it was quite easy to work with optionsets, since it offered both the optionset value (int) and the optionset label (name) in the dynamic content: And here we go, these are our results: Common Data Service Since the Dynamics 365 connector has been deprecated, this is the connector you should use. If you perform a "Get record" or "List records&

Send e-mails with a link to the record via Power Automate

Today we gonna have a look at how to send an e-mail with a link to a CDS record via Power Automate. In the good old classic workflows, you could directly reference the "record URL" from the dynamic data. But since UCI has been launched and you have the possiblity to target different apps, you already had to do a few more steps in the classic workflows as well. The URL to a CDS record consists of multiple things: CRM URL appid entity name record id So we will work this out one after the other. First we add a "List record" action to lookup the appid of the app, we target. We look for "model driven apps" and filter by the name of the app: Then we initialize a variable with the resulting app id: Then we initialize another variable and extract the CRM_URL: Then we fetch our records, where we want to send out a notification with a link, in this case we look for workorders fullfilling certain criteria: Now we compose the record URL: As a next step we create a new