This week I needed to use the List Records function, and I realized that I had no idea how to use the filters. Thank you Jonas Rapp for creating the FetchXML Builder!! The function “Flow List parameters” saved my day:)
Let’s begin with the simple filters where I get a contact with the last name of Sandsør
Test your search result with the Execute button so see that anything is actually returned. Then open the Flow List Parameters
The tool converts the Fetch XML, and magically gives the correct filter to add in our FLOW query. It can’t get much simpler than that!!
Lookups act a little bit different with the syntax, as lookups always to. This got me quite confused before finding this tool, because I was not getting match to my result.
I am searching for contacts with a given GUID. In my case I didn’t know what the GUID was, so I randomly generated a GUID for the formula. In FLOW I substituted the GUID part of query with a dynamic variable.
Filter Query with lookups, you need to add “_” as seen above. When working with lookup you won’t get at match without the “_LookupField_Value”.
Filter linked entity
The last filter is a little more complex, and might not get used due to some limitations of Odata (Must match on unique ID for related).
In this scenario I wanted to locate all contacts with last name “Sandsør” where the regarding accountID = GUID.
Choose the main entity on top, and add “link-entity”
Make sure you have the correct relationship here. Some Lookups support more than one entity, and therefore you make sure you have the correct one.
Again we find the magic with the “Flow List Parameters“.
In this scenario we also get Expand Query result that we need to copy/paste.
Apply to Each
Once you have figured out what filter to use, you can select the “Apply to Each” function, and add custom logic in here.
Dear VOC, Thank you for services provided, but you have been replaced with a younger and more exciting model.
During a call today Microsoft made it quite clear that you should start the transition to FormsPro. On the questions regarding what we do with existing customers, the answer was pretty clear “you should transition”. The one thing that I did think was a little strange was the fact that Microsoft said they would provide assistance migrating (a tool of course). Usually Microsoft doesn’t provide any form for tool for transitioning, and make the partners do this manually.
I might sound negative, but honestly I think it is quite amazing. VOC turning into a separate app on top of the CDS only commits that MS is really serious about the PowerPlatform story and APPS. Microsoft chose to store data in the CDS, so the options for this tool are almost endless. And even more, you don’t need Dynamics to deliver the product.
So what will happen to the product now that it is no longer a Dynamics product? Good question. It was mentioned that licensing is in the works, so let’s hope that this won’t become another Marketing “scandal”. The only thing I would prepare for is a license that now cost more than what you pay today. You can hope for the P2 license to cover this, but probably no.
No one used VOC besides Dynamics customers with the license included. Being able to configure this product separately, you can use any system with a CDS connector. This will open a marked for the FormsPro that the VOC never had. The demonstration was used with Salesforce and Dynamics.