Dynamic Objects - what am I missing ?

[poyntzj]

I have copied an OOB Microsoft 365 flow and need to amend, but Dynamic Objects are killing me.

In the above, for the external ID, it is showing 6, Users, Azure AD Object ID.

I know to cannot be 6 as that is the if statement, so makes sense to be the data from 8, which is a Dynamic object for Users, but it has nothing, no way I can choose anything

In the shot below, you will see I am in a copied version of the flow and I am trying to add the OOB step to try to replicate this, but I cannot see anything into the Users Dynamic Object and cannot add to it.

Any suggestions on how to do this, of what kind of magic SNC have used ?  I cannot see anything in their Action - or a copied Action that would help, and the documentation has not really helped - I did wonder if there was a table with a list of dynamic contents, which only makes sense for a copied Action and not the OOB one.

I need to copy their flow and some of their actions to make specific changes.  All the SaaS integrations I have done so far as great, bar this one - and it is the only one with a Dynamic Object

[-O-]

Dynamic inputs are really finicky.

Those are based on Flow Actions that retrieve some data from somewhere and spew out "pill definitions".

So it may be that Action "Look Up Dynamic CRM Users" is calling the Action providing the pills for its output, but that Action (I don't know which it may be) for some reason is not working.

It is also possible that you have modified Action "Look Up Dynamic CRM Users" after you have used it in "Update Multiple Software Subscription Records".

If that is the case, you need to remove step 11 and add it again.

But most likely it is both.

So make sure the action in step 10 can successfully get and produce the output pills and once you have 10 finalized and only after that, add step 11 again.

[poyntzj]

Thanks for the comment.  The "Look Up Dynamic CRM Users" is from the Microsoft 365 spoke and is protected, so I have a copy of it which is also not working, but I thought I'd try the OOB one incase the "copy" did not quite copy correctly.

That step goes off to an API to retrieve data and is basically the response body.

The original subflow is part of the SaaS license app and I have a copy of that which is what I am working on to make it call the "copied" action

I did wonder if it was something I did, or was missing something elsewhere (linked config in another table somewhere), but as the original Action is also doing the same thing I guess not.

I will try to dig a little more, but I may have to rework my copied action and make sure returns what I need with a standard object and not dynamic.

There is something else with these on the integration profiles where it can obtain a version, but you cannot if you have a reference (it is a connection attribute), which is annoying.

[-O-]

It is very likely that some authentication must be configured so that the Look Up Dynamic CRM Users action will be able to connect to Dynamics to retrieve the schema so that it can "build" output Users.
That's towards which I'd try to steer the investigation.

[poyntzj]

I have thought of that, but at the moment not able to connect and the SME I need to talk to at the client is busy today.

That then gets to the reason why I am copying the SNC flow an action.  SNC have hard coded a connection alias (which can also get the version from the "connection attributes" related list), but I need to be able to pass the connection alias depending on what is being processed and that is the key change. Instead of the connection alias being hard coded, it is now an input variable.

Works fine on the others subflows and action, but with this subflow and its dynamic object, it has me.  if it is doing a looking based on the connection alias that is going to cause me problems....

maybe, if it is that, then if I set a default value for the input variable, I wonder if that would work too...... let me find out if it is establishing a connection and using that first)i

Think I will have to wait for the SME and get a connection, run the original version and see the response body and create a standard object - not a problem really, but is just a lot more documentation and ensuring the client understands if they go to fix or reapply post an update to the OOB spoke and functionality.