A few years back we developed an AutoNumber solution that enables the implementation of AutoNumbers for Dynamics 365 and the Common Data Service. This AutoNumber solution allows the creation of rules for simple autonumbers with prefix, suffix and number of digits, but also has a lot of advanced features for getting numbers from related fields or option sets.
We have all been affected by the COVID-19 outbreak one way or another and have started getting used to a new reality, whether it is working remote, not being able to go to work or even worse have gotten infected by the virus. A few weeks ago (March 8), the mayor of New York City, Bill de Blasio said that the city would provide relief for small businesses across the City seeing revenue reduction of 25% or more because of the COVID-19 outbreak.
I am current engaged in a project where a vendor suggested to the customer to use the same entity for various purposes. That decision might have worked for some organizations, but it did not have a foresight of the future requirements of the organization.
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.
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 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 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 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 series of posts, I will demonstrate how to integrate between Eventbrite and the Power Platform by creating a Model Driven App to store event information, Creation of Microsoft Flow to execute when a new event is created or a new order is added to an event in Eventbrite, and the creation of a Custom Connector to retrieve the event details from Eventbrite.
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.
