Microsoft Dynamics Integration
Ambition’s Integration Solutions team offers various integrations service options to our customers.
If you’re interested in utilizing our integration services for the Dynamics integration and would like more information on associated costs, contact your Ambition representative.
Microsoft Dynamics Integration Overview
Integrating Your Data
Ambition will build a custom integration by leveraging Tray.io’s data connector API services between your Dynamics instance and Ambition.
While Ambition handles all the API and configuration work for you, a Dynamics Admin account is needed to authorize access to your Dynamics data.
Ambition supports metrics related to the following Dynamics data types including, but not limited to:
- Accounts
- Opportunities
- Contacts
- Activities
- Phone calls
- Appointments (meetings)
- Emails
- Tasks
- Custom Entities
See examples of Dynamics metrics here.
Tray.io
Our Dynamics integration solution is built and stood up on Tray.io’s platform. Tray.io is our partner in building and automating how we access, enrich, and process your data. The Tray platform takes maximum precaution to ensure your data remains safe and secure. All data that is processed by Tray is encrypted, review the following links to read more about their Security Standards:
Setting up the Integration
The overall process for getting up and running with the Dynamics integration solution is quite simple. Here’s a quick glance at the time line and actions involved in getting launched!
1. Create an Integration-specific User in Dynamics
An integration specific user is needed to authorize the API between Dynamics and Tray.io. Tray.io is the bridge between Dynamics and Ambition.
Our custom integration uses a Tray.io-hosted OAuth app, which simplifies the authentication process and allows us to limit and specify the exact scopes we need.
Dynamics Admin credentials are needed to permit Read Access to the data from the Entities that support the metrics you want in Ambition. The recommended best practice is to use an empty seat/license to avoid any potential issues.
Username example for your Integration User: ambition-integration@yourcompanydomain.com
2. Complete your Metric Details Sheet (provided during implementation planning)
The metric details sheet is an organized list of the metrics you want to build into Ambition.
The list will include the following details about each metric:
- Metric Name (Display name for your metric in Ambition)
- Description (Additional key details about the metric for clarity)
- Validation Report URL (Link to the report where you track this metric today)
- Entity type (E.g. Call/Task/Opportunity)
- User Field (The user who should get credit in Ambition)
- Date Field (The date the user should get credit in Ambition)
- Count, Sum, or Average (How the metric should be calculated)
- Filter logic
3. Integration Authentication Call
Once you’ve created your Integration User and completed your metric details sheet, we will schedule a call with you to request access to your Dynamics account and enable the integration solution.
During the call, you will be provided with a link to walk through the configuration setup wizard where we will set up a new authentication, authenticate using the OAuth App by signing in with your Integration User’s credentials, and then you will authorize access to the Dynamics API Entities and Properties needed to build your metrics.
4. Integration Build
After the authorization call, the Ambition team will take the information from your metric details sheet to build out your specific use-case solution.
This includes building out the integration tiles in your Ambition account, formatting all of the data, selecting your entities, authenticating your Ambition endpoints, and setting up all the details surrounding the integration solution.
Once data is flowing into your Ambition account, the process of building and validating metrics can begin.
Metrics
You may have a number of potential metrics that you would like to bring in from Dynamics, and we look forward to seeing your list!
The following is a non-exhaustive list of example metrics supported by our integration with Dynamics:
Activity metrics:
Call metrics:
Email metrics:
Account metrics:
|
Appointment metrics:
Task metrics:
Opportunity metrics:
Contact metrics:
|
Upload Frequency
This integration fires every 10 minutes and fetches all new and updated records from the past 10 minutes.
- Up to 1000 records per API request per endpoint
- Up to 4,000 records per minute
Can the frequency be increased?
As we move to improve the processes within the integration we hope to increase sync frequency to 5 minutes and eventually even faster. For now, it will take up to 10 minutes between data creation/updates in Dynamics and metric attribution in Ambition.
How many API requests are made on a daily basis?
Currently, the integration is configured to include 1000 records per request. While the Dynamics limit is 5000 per request, we do not max this out as there is a 6mb data limit
TIP: If you know roughly the amount of records that are created in a day at your company, divide that by 1000, and you will get the number of requests that are made to your Dynamics account.
Deleted Records
We strive to be able to support deleted record functionality for all our integrations. This helps true-up any mistakes or issues that arise when a record is deleted in the software application we’re integrating with.
To ensure your data is accurate, Ambition will run a true-up process to handle deleted records every hour. Dynamics’ native auditing functionality allows for changes and deletions of records for any entity to be recorded and logged within Dynamics as an ‘audit’ record. Our integration queries the ‘audits’ endpoint looking for audit records where the operation/action is a deletion.
The ‘Auditing’ feature must be enabled in your Dynamics instance to allow our processes to capture deleted records and reflect up-to-date metric values in Ambition. The Ambition Solutions team will guide you in enabling this setting, which is configurable for all entities and fields. You may opt to enable it for all entities and fields within your instance or limit to only those used by Ambition.
Historical Data
A historical import is optional, and does require additional approval. If you wish to request a historical import, please note we currently support up to 30 days of historical data.
Making Changes
Our solutions team is here to help you make any changes you may need with your integration solution. Let us know what changes may be needed, and we’re happy to take care of it!
Comments
0 comments
Please sign in to leave a comment.