Eventbrite to CDS Integration – Part 2 (Eventbrite Settings)

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.

Eventbrite to CDS Integration – Part 3 (Custom Connector)

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.

Eventbrite to CDS Integration – Part 4 (Event Flow)

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.

Eventbrite to CDS Integration – Part 5 (Attendee Flow)

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.

Using Flow to get the country of a website visitor

There are many tools for tracking visitors and page views to web sites, but in certain circumstances this might be something that you would want to implement on your own. It is simple enough to get the IP address of the visitor of the web site, but usually in order to get the country we need to call some sort of API. There are various API provides that can give you this information, and in the case of this blog post, I selected a provide called ipgeolocation (ipgeolocation.io).

Generate Document Templates in CDS using Flow

One of the features in Microsoft Dynamics 365 (and some of the previous versions has been document templates). I wanted to validate some of the logic, if we can automate the creation of a document and sending it as an email using Microsoft Flow, and of course Flow did not fail to perform.

What new in the Common Data Service Connector?

With the Power Platform Wave 2 release, we started noticing some progressive changes to the Common Data Service connector. When you do a search for “Common Data Service” in the connector search box, you will see two separate connectors. The first connector which we are used to is still called the Common Data Service connector, but you will notice that there is an additional connector called Common Data Service (current environment) connector.

Microsoft Dynamics 365 and Power Platform 2019 Release Wave 2

The Microsoft Dynamics 365 2019 Release Wave 2 is not available for early adopters. The release is scheduled to start deployment to production environments starting in October of 2019. During August and September, Microsoft Dynamics customers check out the upcoming list of updates that will be released in October.

Dynamics 365 Connector in GCC

Recently I had to work on a PowerApps/Flow solution that would connect to a Dynamics 365 data source. I have done various things previously with the Dynamics 365 connector, but when trying to do the same in my GCC environment, I could not see the Dynamics 365 connector. I thought it was removed, but then I checked my commercial environment and it was there.