Often times, while using Power Automate with Dataverse, you may have come across scenarios where it was difficult to identify the entities with same names.
When trying to pick entities with same names, like Attachments, so we don’t need to guess when you can confirm.
So, you can use Peek Code to take a look at the entity name i.e. the backend name of the entity which you have picked –
- Click on the 3 dots on the action, and select Peek Code.
- And as you can see, you can identify which entity is selected with the same name. You’ll need to know the correct backend name which you intend to select.
I also suggest this is useful when picking other options elsewhere. Do let me know in the comments below as to where all you applied this. 😊
Hope this was useful!
Here are some Power Automate posts you want to check out –
- Blocking Attachment Extensions in Dynamics 365 CRM
- Upgrade Dataverse for Teams Environment to Dataverse Environment
- Showing Sandbox or Non Production Apps in Power App mobile app
- Create a Power Apps Per User Plan Trial | Dataverse environment
- Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
- Co-presence in Power Automate | Multiple users working on a Flow
- Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
- Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
- Call a Flow from Canvas Power App and get back response | Power Platform\
- FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
- Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
- Asynchronous HTTP Response from a Flow | Power Automate
- Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
- Converting JSON to XML and XML to JSON in a Flow | Power Automate
2 thoughts on “Identify entities with same names in Dataverse Power Automate connector | [Quick Tip]”
Reblogged this on Nishant Rana's Weblog.
I’ve just used this to find the correct field in dynamic data, having two fields with the same display name. Another way to do that is hover over the field in the action. But peek code is the best for choosing the right entity, as you’ve mentioned.