Skip to content
English
  • There are no suggestions because the search field is empty.

Integrate Dynamics 365 with BigMarker

Export users and registrants from BigMarker to your Dynamics 365 lists and events

Note: This feature is available to Events and Enterprise plan holders. If interested in utilizing this feature, then please contact your BigMarker customer success manager or an events expert at 

With the Dynamics 365 integration, you can take the registrations you collect on BigMarker and export them to your leads, contacts or even individual events on Dynamics 365.

Contents

  1. Getting started
    1. Creating the app
    2. Authenticating the app
    3. Create roles
    4. Create the S2S app
  2. Connect to BigMarker
  3. Exporting Leads and Contacts 
    1. Creating alternate keys
  4. Exporting event registrations

Getting started in Dynamics 365

Before connecting to BigMarker, there are a few steps that you'll need to do within your Azure and Dynamics 365 environments.

Create a new app

While logged into your Microsoft account visit this URL to get started:

Once you're logged in to Azure, click the search bar at the top, search for and click "App Registrations." Once you get to the App Registrations page, click on "New Registration."

With this new app, give it a name and leave the Supported account types settings to their default. In the Redirect URI setting, choose "Web" for the platform and enter this in the path:

http://localhost

Create the application, and you'll first see the overview page. Here you'll find the Application (client) ID and the Directory (tenant) ID. You will need these two values when you enter in your information into the BigMarker integration settings. 

From the left-hand menu click on ManageCertificates and Secrets. In this page, click on New client secret, give it a description and an expiration time, and click Add.

IMPORTANT: Client secret values cannot be viewed, except for immediately after creation. You must copy the secret value immediately after creating the client secret. The value will be used in the BigMarker integration settings under Client Secret.

Authenticating the App

With the app created, there are some additional steps to authenticate it. The full details on app authentication can be found at this link on Microsoft's learning resources. To do so, follow these steps:

  1. Start with this URL
    https://login.microsoftonline.com/common/adminconsent?client_id=aaa&state=12345&redirect_uri=bbb
    1. Replace common with the tenant ID found in the app overview page
    2. Replace aaa with the client ID found in the app overview page
    3. Replace bbb with https://localhost
  2. Take this URL and open it in an incognito window
  3. After logging in to your MS admin account, you will be asked to grant permissions to the app. you will see a new page. After agreeing you will be redirected to a blank pageandthe URL will contain admin_consent=True

Create the roles in your app

With your app authenticated, you now need to make roles in that app that have specific access. While logged into your MS admin account visit https://make.powerapps.com/ and click on Power Platform and the Admin Center.

In the admin center, click on manage to see your environments, and click on the one you are working with. Then click on Security Roles then Add Role.

After creating the role, you will grant it specific privileges to the different objects and the ability to modify them. For this integration, you will allow access to leads and contacts. Use the search bar to search for these objects, then grant permission to all columns by changing the value to Organization. Save once you change the permissions for all of them.

Create the S2S App

Go back to the first screen where you are managing the environment and click on the S2S app See all link. In the next screen, click on New app user

In the settings, first choose an app to associate this user with. This will be the app that you created in the previous step within Azure. If you have many apps, you can search for it by name.

In the business unit field, you may get a dropdown of available environments, but you may need to enter this in yourself. This field should use the organization ID found in your Power Platform Admin settings. Look for the Environment URL and take the ID at the beginning of the URL. Paste that value into the Business unit field. 

For the Security Roles settings, choose Basic User and System Administrator.

Connect to BigMarker

Now that you have done this work in your Dynamics environment, we're ready to connect to BigMarker. Use this guide to see what value should go in which settings:

  • Tenant ID - This is the Directory (tenant) ID found in Azure
  • Client ID - This is the Application (client) ID found in Azure
  • Client Secret - This is the Secret Value that you needed to copy from when you were creating the app in Azure
  • Dynamics 365 Instance API URL - This is the Environment URL that you see in the Powerapp admin settings

IMPORTANT: You will need to add .api into the URL. You will put this inbetween the organization ID and the subdomain. So:

https://org306d4fab.crm.dynamics.com/

becomes

https://org306d4fab.api.crm.dynamics.com/

Be sure to use the URL with .api in the BigMarker field

Exporting Leads to Dynamics 365

Create alternate keys

In order for registrant exporting to function correctly, you'll need to make alternate keys for your leads and contacts. Within Powerapp, go to Tables and search for Leads (and/or contacts). Open it and then click on Keys.

Create a new key then give it a name and assign it to the Email column. Save it to finish making the key. Note: the status starts as pending for this alternate key and the integration will not function until the status is Active. Do this process for both leads and contacts as needed.

Mapping fields

To map BigMarker registration fields to Dynamics 365, you will need to get the logical name for those fields. When looking at the settings for either contacts or leads, click on Columns.

You'll now see a list of fields available for this object. Find a field, then in the 3-dot menu got to Advanced > Tools > Copy logical name

You'll need to paste this name for each field in the BigMarker integration settings that you want to map.

 

Export event registrations

To begin exporting event registrations, visit your Environment URL and go to the Settings and got to the page for Web Applications. Create a new application.

For the name you can give it any name

For the origin, you need to put in the BigMarker domain, which for most users will be https://bigmarker.com but for others it might be https://web.bigmarker.com

Once saved, open the new application by clicking it's name and find the token and the endpoint. You'll need to copy and paste this into BigMarker.

Once you save this information on BigMarker, you can edit the dropdown field for selecting the Dynamics 365 Event, which will have all the events associated with this environment. Select on to export registrants to.

Note: your event must be live & published on Dynamics 365 in order for the export to work.

Just like for contacts and leads, you'll need to get your fields from your Dynamics 365 event and map them to corresponding BigMarker fields. Visit the Event Planning dashboard and open up your event. Click on Form, then Edit.

In the new edit window, click on a form field to view it's logical name for you to copy and paste into BigMarker.