This is a scenario I came across when I was using Common Data Service connector [not Common Data Service (Current Environment)] connector to read Opportunities tied to an Account.
Example
In this scenario, I wanted to retrieve the Opportunities tied to an Account. So, my filter query was _parentaccountid_value(‘ACCOUNT_IDENTIFIER’)
Here’s my Flow starts. I want to read Opportunities that are…
Continue Reading priyeshwagh777’s Article on their blog
Using Parse JSON to read individual List Records in Flow|Power Automate
This is a scenario I came across when I was using Common Data Service connector [not Common Data Service (Current Environment)] connector to read Opportunities tied to an Account. In this scenario, I wanted to retrieve the Opportunities tied to an Account. So, my filter query was _parentaccountid_value(‘ACCOUNT_IDENTIFIER’) Here’s my Flow starts.
Blog Syndicated with priyeshwagh777’s Permission
More About This Author
Array
- Dyn365CE2 April 2024Update SVG Icon to Custom Entity in Sitemap | Model Driven Apps
- Dyn365CE1 April 2024Preferred Solution in Dataverse | Power Platform Admin Center
- Dyn365CE18 March 2024Button to send Email based on Templates in Dynamics 365 CE
- Dyn365CE18 March 2024Use Monitor to debug Model-driven apps remotely | Power Platform