Let’s keep going on our work with Dynamics 365 Customer Voice and Power Automate! As we learned last week, the data from Dynamics 365 Customer Voice is stored in the Dataverse (formerly Common Data Service). However, we want this data in our standard entities such as Contact. So, we are going to use Power Automate to move it into place.
In part 1, I created the caregiver contact record – in system (and, ironically, human) language, this is the “parent” record. Today, I create the “child” contact records and link them to the caregiver. Each parent can have multiple children, so these entities are related in a 1:N (one-to-many) relationship. Yes, one could argue that there would be more than one parent/caregiver. In our fictitious example, we’re going with the logic that there is ‘one parent advocate’, if you will. In the video, I outlined the steps to use in Power Automate and share some issues I worked through. (Here is the post referenced for linking the records in Power Automate.)
That’s all there is to it! This session has been a great exercise to help use learn more about Dynamics 365 Customer Voice and Power Automate. The possibilities are endless!
How can your organization make use of these tools?
This is part of the Power Baseball League Series with Kylie Kiser (follow her on LinkedIn, Twitter or her Blog). You can follow the series on the Power Baseball League Series Page and the Power Baseball League YouTube Playlist as they are added.
You can find Kylie’s content at the following: