Power Baseball League: Customer Voice and Power Automate Build (Part 2)

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.)

Power Baseball League: Customer Voice and Power Automate Build (Part 2)

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 LinkedInTwitter 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:

Blog: https://kyliekiser.com/

LinkedIn:https://www.linkedin.com/in/kylie-kiser/

Twitter:https://twitter.com/KylieKiser

YouTube: https://www.youtube.com/channel/UCt7jIvOwE4mHsr1Tjk1jj3w

Cover Photo: Photo by Jimmy Conover on Unsplash

Power Baseball League: Customer Voice and Power Automate Build (Part 1)

We have been talking for a few weeks about Dynamics 365 Customer Voice and using this to get data into the Power Baseball League. Today we are going to start the Dynamics 365 Customer Voice and Power Automate build!

Keep in mind that the Dynamics 365 Customer Voice data will already be in Common Data Service (CDS) / Dataverse. However, this data is in entities specific to customer voice and separated by question. So we want to move this data into the core entities like Account and Contact.

We talked through some architecture decisions last week. This week, I put our plan into action. I tried to break it down and show you how the data processes through Power Automate to help you understand the process.

Dynamics 365 Customer Voice and Power Automate Build (Part 1)

Stay tuned next week when I take this a step further and use Power Automate to create the child records and link with the parent record created today!

This is part of the Power Baseball League Series with Kylie Kiser (follow her on LinkedInTwitter 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:

Blog: https://kyliekiser.com/

LinkedIn:https://www.linkedin.com/in/kylie-kiser/

Twitter:https://twitter.com/KylieKiser

YouTube: https://www.youtube.com/channel/UCt7jIvOwE4mHsr1Tjk1jj3w

Cover Photo: Photo by Keith Johnston on Unsplash

Power Baseball League: Customer Voice and Power Automate with Special Guest Todd Mercer

It’s time for another special guest! Todd Mercer (BlogLinkedInTwitter) joins the Power Baseball League crew to talk about Customer Voice and Power Automate. We talk through how the Dynamics 365 Customer Voice responses come in to Dataverse (formerly Common Data Service). Then how we will use Power Automate to move that data around.

This is a great discussion where we discuss multiple ways the solution could be architected. Plus talk through some of the constraints to keep in mind. We hope you enjoy listening to us work through our struggles to make a plan with actionable next steps!

Power Baseball League: Customer Voice and Power Automate with Special Guest Todd Mercer

How would you solve this same issue? What other ways could we architect this solution?

This is part of the Power Baseball League Series with Kylie Kiser (follow her on LinkedInTwitter 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:

Blog: https://kyliekiser.com/

LinkedIn:https://www.linkedin.com/in/kylie-kiser/

Twitter:https://twitter.com/KylieKiser

YouTube: https://www.youtube.com/channel/UCt7jIvOwE4mHsr1Tjk1jj3w

Power Baseball League: Dynamics 365 Customer Voice Creation

Let’s continue the Power Baseball League journey by starting the Dynamics 365 Customer Voice creation process!

So far we’ve talked about getting data into our system via manual import (hello historic spreadsheets!). Next we tackled Forms Processing to handle any hand written applications. Finally, last week built out a Power App to take a snap of the form and processes it. From a picture directly into the system – Amazing!! 

Now, we want to empower our applicants to input data directly into our system on their own! This is the ultimate organizational efficiency goal as it means our team doesn’t need to do anything. No messing around with imports, no taking pictures of forms and hoping they don’t have any readability issues. This puts the power of data entry onto the registrant themselves. All we have to do is review the data as it arrives. Sweet! 

There are several parts to this. This is one of those situations where we’ll need a bit of extra work up front. First, we needed to build out the webfrom itself. We built this using Dynamics 365 Customer Voice.

In a few weeks, we will show you how we take this submitted data and move it around. Using Power Automate we will shift data from the form submission over to our Power Baseball League data management system.

Creating the Customer Voice and sharing some laughs along the way!

NEXT STEPS

Now it’s your turn! Turn on Customer Voice in your environment and build a form. This data will go directly into Dataverse (Common Data Service). Then you can determine what to do with each data element. More on this to come after Thanksgiving.

What’s next for you? What forms could your organization benefit from?

This is part of the Power Baseball League Series with Kylie Kiser (follow her on LinkedInTwitter 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:

Blog: https://kyliekiser.com/

LinkedIn:https://www.linkedin.com/in/kylie-kiser/

Twitter:https://twitter.com/KylieKiser

YouTube: https://www.youtube.com/channel/UCt7jIvOwE4mHsr1Tjk1jj3w

Cover Image: Photo by Savannah Rohleder on Unsplash

Power Baseball League: Add Forms Processing to a Power App

Last week, we set up a Forms Processing Model. Today we are going to add Forms Processing to a Power App! This simple App will allow us to take a snapshot of the application and get the data. Then all this data will be fed directly into our CDS Environment. The app can be created in 15 minutes or less and creates huge organizational efficiencies!

This video starts with the model already up and running. We will walk through the full set up of the Power App. This includes embedding the Forms Processing component and then submitting this data through a form. It will be a simple yet functional app that we can improve on later.

This app will make it even easier for the Power Baseball League team to get hand written registrations into the system!

Kylie works through the process of adding forms processing to a Power App

RESOURCES ON HOW TO ADD FORMS PROCESSING TO A POWER APP

How have you used this technology for your organization? Share your Forms Processing success stories with #PowerBaseballLeague and let’s learn together!

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:

Blog: https://kyliekiser.com/

LinkedIn:https://www.linkedin.com/in/kylie-kiser/

Twitter:https://twitter.com/KylieKiser

YouTube: https://www.youtube.com/channel/UCt7jIvOwE4mHsr1Tjk1jj3w

Photo by Eduardo Balderas on Unsplash

Power Baseball League: Build a Forms Processing Model

Last week we talked about getting started with a Data Import so we want to look at more ways to keep bringing data into the system. That means we are going to build a Forms Processing Model!

You may remember our first attempt at the forms processing function with Phil Topness a few weeks ago was based on the historical registration form for the Power Baseball League. In the spirit of finding efficiencies and simplifying process, we decided to shorten the form, both to make it easier for people to sign up, but also to simplify the form processing model. 

During this video, Kylie sets up and trains the model for the improved form! Take note of how short this video is. It is super quick and easy to create and train the model!

FORMS PROCESSING RESOURCES

To get started on your own, check out these docs resources:

I hope you learned from today’s quick video! What forms are you going to start processing?

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:

Blog: https://kyliekiser.com/

LinkedIn:https://www.linkedin.com/in/kylie-kiser/

Twitter:https://twitter.com/KylieKiser

YouTube: https://www.youtube.com/channel/UCt7jIvOwE4mHsr1Tjk1jj3w

Cover Photo: Photo by Matthew T Rader on Unsplash

Power Baseball League: Let’s Get Some Data!

What good is a system if we don’t have any data in it?! Today, we start the journey to add some data and we are going to start with the basics of data import within the solution itself.

In this video, we will set the tone for the next portion of the series where will be recording 3 ways to get data in:

  1. Data Import: This is a great way to deal with our historical data. We are assuming that this data was previously managed in Excel. So we can use this to populate the system we have been creating.
  2. Forms Processing: As we discussed with Phil Topness, we are going to look at creating a simple Forms Processing model with AI Builder. Then we can build a Power App that will consume that model.
  3. Dynamics 365 Customer Voice: Finally we will revisit our discussion with Megan V. Walker to show how we can create a webform to gather data and bring in to Common Data Service.
It’s almost opening day – but we need some data to get started!

NEXT STEPS

If you are looking to do this in your own environment you can also review these Microsoft Docs:

How do you use Data Import? What data is your business currently managing in Excel that you can or should bring into CDS?

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:

Blog: https://kyliekiser.com/

LinkedIn:https://www.linkedin.com/in/kylie-kiser/

Twitter:https://twitter.com/KylieKiser

YouTube: https://www.youtube.com/channel/UCt7jIvOwE4mHsr1Tjk1jj3w

Cover Photo: Photo by Jimmy Conover on Unsplash

Power Baseball League: Dynamics 365 Customer Voice with Special Guest Megan V. Walker

This was such a great discussion! Megan is THE go to when it comes to Forms Pro and Dynamics 365 Customer Voice, so we were thrilled to have her join us. She also happens to be a genuinely awesome person to talk to so it was tough to keep this one short.

Previously we had created a system and begun configuring it to meet he needs of our Power Baseball League. As we went, we started talking about how data would be flowing into the system. We wanted to explore our options, and last time we discussed Forms Processing as a way to get paper-based, hand written data into our database. However, not everyone has a printer and we might need to capture larger amounts of data from some people. Enter Dynamics 365 Customer Voice!

Customer Voice allows us to build a form where users will enter in the data. This data is automatically stored in Common Data Service (CDS) and ready for us to use within the Power Platform!

CALL THE DYNAMICS 365 CUSTOMER VOICE EXPERT!

We called in a Dynamics 365 Customer Voice Expert to help us with this discussion – Megan V. Walker! Megan talks us through how to plan out our form and next steps. Additionally, we also talk about some concerns with our data and potential solutions.

The ever delightful Megan V. Walker joins Kylie and I to discuss the power of Customer Voice. Not going to lie, I had a bit of a fanboy moment!

Thank you to Megan for joining us for this discussion, make sure you subscribe to her blog content, connect on LinkedIn and follow her on Twitter!

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:

Blog: https://kyliekiser.com/

LinkedIn:https://www.linkedin.com/in/kylie-kiser/

Twitter:https://twitter.com/KylieKiser

YouTube: https://www.youtube.com/channel/UCt7jIvOwE4mHsr1Tjk1jj3w

Cover Photo: Photo by Nick Jio on Unsplash

Power Baseball League: Forms Processing with Special Guest Phil Topness

During our discussions up to now we’ve talked about how many of our constituents will need to continue filling in paper application forms to register their children in the up-coming season. To that end, we wanted to make sure our solution had a tool that could automatically read data, even hand-written information, from a form. Enter Forms Processing.

Phil, Principal Program Manager at Microsoft (and near honourary Canadian, he just needs a shot of maple syrup!), joins us to talk about his irrationally excited take on the potential of forms processing to help us in our project. We not only talk through it, but we also dive into the tool using our hand-written application forms and see it unfold in real time during the call.

THIS WAS SO COOL!!! Seeing a form that was filled in by hand get submitted and read – with excellent accuracy to boot – was super cool. There is no question this will benefit applicants for the Power Baseball League registration – the time savings alone will equate to hours saved entering data. There is only one word: WIN!

It’s clear this functionality has the potential to find efficiencies for any organization that needs to read data (printed or hand-written) into a system, and Phil’s enthusiasm about the topic is infectious! Many thanks to Phil for joining us on this video!

Forms Processing with Special Guest Phil Topness!

Phil Topness

LinkedIn: https://www.linkedin.com/in/topness/

Twitter: https://twitter.com/topness

YouTube: https://www.youtube.com/c/topness

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:

Blog: https://kyliekiser.com/

LinkedIn:https://www.linkedin.com/in/kylie-kiser/

Twitter:https://twitter.com/KylieKiser

YouTube: https://www.youtube.com/channel/UCt7jIvOwE4mHsr1Tjk1jj3w

Cover Photo: Photo by Keith Johnston on Unsplash

Power Baseball League: Custom Entities

In our last post, we set up a Model Driven App. CDS provides a fabulous foundational set of entities to work with, but sometimes we need to add our own flare to the system to ensure it meets organizational requirements. To this end, we’re at the stage where we want to create some custom entities to go with the out of the box entities.

We will work through the creation of a custom Registration entity to track each new application. We also create a Season entity and build a few relationships. Plus field creation, form editing, and adding these entities to the Model Driven App.

Join us as we walk through these steps.

Power Baseball League: Custom Entities

We hope you are enjoying our unscripted walk through of these concepts. In this video we made a few missteps as we are still learning too! But we also shared several great tidbits (or timbits for our Canadian friends!) around planning best practices, relationships and currency fields.

What entities are we missing? What would your next step be?

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:

Blog: https://kyliekiser.com/

LinkedIn:https://www.linkedin.com/in/kylie-kiser/

Twitter:https://twitter.com/KylieKiser

YouTube: https://www.youtube.com/channel/UCt7jIvOwE4mHsr1Tjk1jj3w

Cover Image: Photo by Savannah Rohleder on Unsplash