It is a very trivial scenario that we would want to create a Common Data Service entity record from a web page. An example can be a contact us page or request for help that would create a lead or a case in Microsoft Dynamics backend. Although Dynamics Portals (and now Power Apps Portals) are available for this kind of integration, many organizations still use other types of web applications and they need to integrate with the Common Data Service, such as various web to lead products.
Over the past couple of years, since the release of Unified interface, one of the biggest pain points for most customer was that features that are available in the web client are not available in the new Unified Interface. There were a lot of improvements in the Unified Interface with the responsive client, custom controls and more, but when you are used to working in a certain way, taking away features is sometimes hard to get used to.
While most of you might not be experiencing this issue, it is still a good workaround for a situation that you might have. Recently we had a situation that when we tried to retrieve the account record using the Get record action in our Government Cloud instance, but the results did not retrieve all the attributes. The attribute that we were really having an issue with was the address1_name.
In a recent blog I posted a few days ago, I posted how to use Azure Service Bus and a Listener application to integrate between the Common Data Service (Dynamics 365 or Power Apps Model Driven Application) and an On Premise SQL Service database. As mentioned that there are a few easier ways to implement this, I wanted to demonstrate how easy it would be to perform similar functionality using a Microsoft Power Automate Flow that connects to the On-Premise Data Gateway
In this blog post I will demonstrate how to use Azure Service Bus and a Listener application to integrate between the Common Data Service (Dynamics 365 or Power Apps Model Driven Application) and an On Premise SQL Service database.
In the final post, we will quickly view the results of this entire process. We will create an Event in Eventbrite, and add an attendee to this event, and then verify that the Event has been created in CDS as well as Attendee added to the Contacts entity and linked to that Event.
In this fifth post we will update the original flow that we created for when a new attendee is registered in Eventbrite. Your flow should have a couple of steps as the baseline. The steps include When a HTTP request is received, and the Initialize Variable action.
In this fourth post we will update the original flow that we created for when a new event is created in Eventbrite. The flow should have a couple of steps as the baseline. The steps include When a HTTP request is received, and the Initialize Variable action.
In the third post will create our custom connector in order to connect with Eventbrite. The custom connector will allow us to call the Eventbrite api to retrieve the required information about the Events and the Attendees that have not been provided by the Webhook.
In the second post will concentrate on the configuration of Eventbrite. We assume that you have already an Eventbrite account and you can create your own events. If you don’t have an Eventbrite account yet, this is the time to create one. You only need an email address and to set a password in order to create an Eventbrite account. Eventbrite is available as a free or paid service. Everything in this series of posts was done using the free Eventbrite account.