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 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.
On one of our recent projects, we had a requirement to only allow valid Tax Id Numbers on that field. There are various ways of implementing this, but as the direction seems to be to shift the development of these kind of features to custom controls, we decided to implement it as a PCF custom control.
A little late in the game as Power Virtual Agent is already in Public Preview and trials are available, but I wanted to demonstrate how easy it is to create a bot, publish it and add it to your Power Apps Portal page.
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.
As part of the 2019 October Release (Wave 2), Microsoft is introducing PowerApps Canvas App Components. Canvas App Components are reusable components that can be shared across multiple screens of your app, without the need to create or copy the component across the multiple screens. Create once, and use multiple times. Canvas App components can also be imported and exported, so that they can be used across multiple applications. This post will demonstrate how to create a simple component, add custom properties and use it from within your Canvas application
As part of the October 2019 release (Wave 2), the Unified Interface will receive a few usability enhancements that will address some of the issues that were reported by the community. These enhancements include: Anchoring error notifications, Viewing inline images for emails that are read-only, Improved usability/density and filtering in views and form header usability enhancements.
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.
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.
