Answered

flow using dataverse legacy trigger

(1) Share

Report

Posted on by StewC

116

I have a flow triggered when a row is selected in one table (Request) of my dynamics365-derived Dataverse app. It works well, and I want to adapt it to work for a different table (Account).

I cloned the flow, then edited the trigger to use Account table, rather than Request. Flow saves, and appears in the app. When I select an Account and try to run the cloned flow, I get this error message:

Error: The input body for trigger 'manual' of type 'Request' did not match its schema definition. Error details: 'Required properties are missing from object: _msnfp_recipientid_value.'.

This suggests to me that the table change to Accounts didn't really take place. So I crossed my fingers, deleted the trigger and re-added the same Legacy trigger. Works fine now. But I'm always nervous when the solution is "erase and retry." And knowing that this legacy connector is due to go away -- is there a more current trigger we should use for building 'selected row(s)' flows that run from within a Dataverse app?

Categories:

Design & build

I have the same question (0)

All responses (2)

Answers (0)

Suggested answer

Michael E. Gernaey 53,433 Super User 2025 Season 2 on at

Like (1)

Report

Hi

I responded on your other post.

Was this reply helpful? Yes No
StewC 116 on at

Like (0)

Report

@FLMike,

Thanks. I couldn't find your response on any of my other posts, but in re-reading the other threads re the legacy vs new Dataverse Connectors, I can see an answer to building a flow triggered in my D365 app:

When I switch back to the old Editor, I can see the When Row Selected trigger in the new Dataverse connector. I can select it and build a flow using it. (FWIW, Had to manually enter the table name first time through, but that worked and on subsequent edits it could offer up the list of all tables in that environment.)

New Flow is available for use in the appropriate table.

For others: note that if you try to build the flow using the Create A Flow submenu in your app, it will still (9/24) select the Legacy trigger.

thx

Was this reply helpful? Yes No