Trigger flows with dynamics CRM custom action.

(4) Share

Report

Posted on by Naresh Veginati

Hi Team,

I have developed custom action and a a cloud flow. When action is called it should trigger flow. MS docs for your reference (docs.microsoft.com/.../action-trigger)

I have written a flow, Which will trigger "when an action is performed", here is the screenshot.

Creation actions,

Created one action with the name "Sample Action" its global action.

Created another action with the name "Sample Action with Account" on account entity with input parameters as "Name".

Created two catalogs,

1. Parent Catalog

2. Child Catalog

Created two Catalog Assignments

1. Using 'Child Catalog' as catalog and 'Sample Action' as assignment.

2. Using 'Child Catalog' as catalog and "Sample Action with Account" as assignment.

but when action is triggered, instead it showing fix flow, when click on it it shows the error message as "Custom steps cannot be registered on internal system global sdk message id: 07efb30f-e574-49a8-befb-c5bac5720afe."

Any help.

I have the same question (0)

All responses (5)

Answers (1)

MattHoy 5 on at

Like (1)

Report
Copy link

Link copied!

I'm also experiencing this issue. I'm attempting to launch a flow using a trigger created for d365 marketing however when I use the 'when an action is performed' trigger I get the same error.

As far as I was aware this was the expected route for launching a power automate flow from a real time marketing journey. Any help would be greatly appreciated.

Was this reply helpful? Yes No
natekist 5 on at

Like (0)

Report
Copy link

Link copied!

I am also seeing this same error message when configuring a trigger based on a dataverse action.

Was this reply helpful? Yes No
softwaredude 5 on at

Like (1)

Report
Copy link

Link copied!

I have wasted many frustrating hours trying to resolve this same issue. Exact same error message, including the GUID. I've carefully rebuilt several times the custom action process, the catalog/category, and the flow (with nothing but the trigger and a terminate step) using different Dataverse connection references. No luck.

Interestingly, I cannot reproduce this issue in another similarly-configured Dataverse environment. The very same setup works there.

At this point, it feels like a platform bug that exists in some environments but not all.

Was this reply helpful? Yes No
Mike McGuinness_ on at

Like (1)

Report
Copy link

Link copied!

Hi Naresh, we're experiencing the same error, but with events (i.e. OnExternalCreated, OnExternalDeleted events) on Virtual Tables and Dataverse flows. Working with MS support, it appears to be an issue with an "SDK Message Processing Step" that is supposed to be in the base solution is missing from our environment. We're waiting on a fix from them. Note the "07efb30f-e574-49a8-befb-c5bac5720afe" Guid in the screenshot of the missing step.

Was this reply helpful? Yes No
Verified answer

Naresh Veginati 40 on at

Like (0)

Report
Copy link

Link copied!

Hello,

This is got fixed by platform itself. Looks like it's known issue and fix could have been applied from update.

Unfortunately i could not check platform updates to provide more details.

Thank you!!!

Was this reply helpful? Yes No