This may not be an everyday requirement but certainly one that picks the brain when the requirement comes. Quickly the part of the requirement is to retrieve the primary attribute name dynamically for the given entity. It didn’t took much time to realize that the OOB CDS’s List action is not helpful, that’s when I found this solution from one of the forum posts. The solution is to use HTTP with Azure AD Connector (see the screenshot below) (Just search for HTTP in the choose action dialog in your flow) .

💡 This is not just for retrieving Meta data but can also be used for executing any other CDS WebAPI queries if required.

To start with, Select HTTP With Azure AD Connector and select Invoke a HTTP Request.

Provide Base URL & Azure AD Resource URL as your CRM url and Sign in.

That’s it, provide your whatever required WebAPI Query and you will be able to execute as long as it is a valid request. Here are some examples..

And the result..

One another example..

And the result..

Happy FLOWing…