Dynamics Community Forum Thread Details

Hello Sandeep,

Based on your description and the Power Automate expression, it might be correct if the Activity ID within the call report link in the email description is consistently enclosed within curly braces {}.

Let's break down the expression:

outputs('Compose_-_Description'): This assumes you have a "Compose" action named "Compose - Description" that holds the email description.

indexOf(outputs('Compose_-_Description'), '{'): This finds the starting index of the first curly brace {.

add(indexOf(outputs('Compose_-_Description'), '{'), 1): This adds 1 to the starting index, so you start extracting the ID after the opening curly brace.

indexOf(outputs('Compose_-_Description'), '}'): This finds the starting index of the first closing curly brace }.

slice(outputs('Compose_-_Description'), ..., ...): This extracts a substring from the email description, starting from the position after the { and ending at the position of the }.

However, there are a few potential issues and considerations:

Consistency of the Link Format: This expression heavily relies on the Activity ID being always enclosed in single curly braces {} within the call report link. If the format varies, this expression might fail.

Multiple Curly Braces: If there are other curly braces in your email description before the Activity ID, indexOf will only find the first occurrence, leading to an incorrect extraction.

Error Handling: The expression doesn't include any error handling. If the curly braces are not found, the indexOf function will return -1, and the slice function might throw an error.

To make it more robust, you might consider:

Verifying the presence of both curly braces before attempting the slice.

Using a more specific pattern to identify the Activity ID if the link structure is more predictable (e.g., if the ID always follows a specific keyword). You could potentially use the split() function if the link has a consistent delimiter.

Regular Expressions (more advanced): For more complex or less consistent link formats, you could use the "Parse JSON" action with a schema designed to extract the ID using a regular expression (though this is more involved).

To confirm if your expression is working correctly for your specific scenario:

Run your flow with a sample email.

Inspect the output of this expression. Does it correctly extract the Activity ID?

If the Activity ID is reliably within single curly braces, your expression should work.

If my answer was helpful, please click Like, and if it solved your problem, please mark it as verified to help other community members find more. If you have further questions, please feel free to contact me.

My response was crafted with AI assistance and tailored to provide detailed and actionable guidance for your Microsoft Dynamics 365 query.

Regards,

Daivat Vartak

Community site session details

Flow retrieve activity

Helpful resources

News and Announcements

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

Featured topics

Product updates