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?
