Substrings in Power Automate

Substrings

Today we will look at an example, how to extract a substring from a given string. Our aim is to extract the file extension of a note (attachment in CDS) from the mime/type field.

Single vs. multiple records

First we fetch our underlying note using either the get record or the list records CDS action:

Depending on the action you choose, the formulas below differ, since "Get record" returns just one single record, while "List records" can return multiple records.

For a single record you will reference your fields like outputs('<Name of your action>')?['body/<'name of your field'>'].

While for multiple records you will have to put your actions into an apply to each "group" and will reference your fields like items('<name of your apply to each action>')?['<fieldname>'].

Extract substring

Once we have added an action to fetch our underlying record:

we are ready to define 4 compose actions, that will result in our substring.

Our starting point is the field "mimetype" of a note --> outputs('GetNote')?['body/mimetype'] and it contains the value "image/png". We want to extract the file extension "png" from this string.

First we have to define the starting point of our substring, by adding a compose action to our flow:

and adding the following formula as an expression:

add(int(indexOf(outputs('GetNote')?['body/mimetype'],'/')),1)

Since we will reference this action in the further steps, we give it a meaningful name and call it StartSubString:

Then we add a second compose action to find out the lenght of our mime/type string, using the following formula:

length(outputs('GetNote')?['body/mimetype'])

In our third compose action we calculate the difference between the length and our starting point, to find out the length of our substring, using following formula:

sub(outputs('LengthMimeType'),outputs('StartSubstring'))

Finally we add a last compose action to put our substring together:

concat('.',substring(outputs('GetNote')?['body/mimetype'],outputs('StartSubstring'),outputs('LengthSubString')))

Result

Lets perform a test run and have a look at our result:

Comments

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 C

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

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. https://flow.microsoft.com/en-us/blog/nine-new-connectors-in-april-and-improved-visibility-into-trigger-failures/ 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&

CRM addicted

Search This Blog