In case it’s your first time creating a Cloud Flow using Dataverse connector and dealing with Primary Key of the Activity Type of entity, here’s a quick tip to keep in mind.

Normal Entity

As a creator for Flow, let’s say you have listed Records of an entity called as Accounts (out-of-the-box), you’ll notice that the name of the entity

Activity Entity

Now, if you try to search for the Name of the Activity entity, it won’t appear as it does for other entities, instead just search “Unique” and you’ll find an entry for Unique identifier of the activity entity –

1. Name of my Activity entity is ‘Snapshot’, but it doesn’t show up when I search Snapshot.
   
   
2. So instead, just search “Unique” or “Identifier”
   
   
3. On the contrary, out-of-the-box entities have their own names named as Primary Keys
   

Here are some more Power Automate / Cloud Flow blogs you might want to check –

1. Split On in Power Automate in SharePoint trigger for Item updates
2. Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
3. Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
4. Invalid XML issue in Dataverse connector for List Rows action | Fetch XML Query | Power Automate
5. FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
6. Invalid type. Expected Integer but got Number error in Parse JSON – Error at runtime after generating Schema | Power Automate
7. Asynchronous HTTP Response from a Flow | Power Automate
8. Converting JSON to XML and XML to JSON in a Flow | Power Automate
9. Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
10. Tag a User in a Microsoft Teams post made using Power Automate
    
    Thank you!