How Can We Help?

Connecting and Authorizing TruSales for Microsoft Dynamics

  • Updated

Follow these instructions to connect and authorize TruSales with Microsoft Dynamics.

Note: The application user permissions required and the minimum required fields for the TruSales integration is shown at the bottom of this page.

 

TruSales Security Roles
Download and import the “TruSales Security Roles” solution to get the pre-configured security role for the TruSales Application User you will create. The security role includes all of the required permissions the application user will need to access the desired organization data.

 

 

First TruSales Login
Follow the TruSales invitation link sent to you by your Primary Intelligence implementation specialist and click on the “Microsoft Dynamics 365” login link to log into TruSales using your MS Dynamics admin account.

trusales ms 1.png

Permissions Request
Once logged in, you will be asked to grant TruSales the permissions it requires to connect with your MS Dynamics environment. Please review the requested permissions and select “Accept” to proceed.

Note: You can check the “Consent on behalf of your organization” option to grant these permissions for other users in your organization.

dynamics 2.png

Select Dynamics Environment
Select the MS Dynamics environment you will be integrating with your TruSales instance.

select dynamics.png

Your TruSales Application ID
Once you reach the “Required Setup Application User” window in TruSales, follow the steps below to import the pre-configured security role, create an Application User in your MS Dynamics environment and apply the security role to the new application user. The application user is used for all data integrations between TruSales and MS Dynamics.

Note: The “TruSales Application ID” value from this window will be needed for the application user.

id.png

Download “TruSales Security Roles” Solution
Download the “TruSales Security Roles” compressed solution file located at the top of this page, or click this link: TruSales Security Roles.

Navigate to the “Solutions” directory. Select “Import” in the action bar.

Note: You can import the solution using either Dynamics or Power Apps. Choose the “Import Solution” section that best suits your organization. This choice will not affect the results of the installation.

dyn3.png

Import “TruSales Security Roles” Solution
Select “Choose File” and select the “TruSales Security Role” compressed solution file.

dyn 4.png

Select “Import” on the Solution Information screen.

dyn6.png

Your Application User for TruSales
Log into MS Dynamics using an account with sufficient permissions to create an Application User. Navigate to the “Security” page under “System Settings.”

dynamics7.png

Navigate to the “Users” directory.

dynamics8.png

Navigate to the Application User View
Use the view dropdown menu to select the “Application Users” view.

Note: If you have not selected the “Application Users” view, you will get an “Add and License Users” popup when you select “NEW” and will be unable to proceed.

dynamics9.png

Create Your Application User
Select “NEW” in the action bar to create a new application user for TruSales.

dyn10.png

Navigate to the Application User Form
Make sure you are on the “Application User” form using the form dropdown menu.

dyn11.png

Apply TruSales Application ID
In the “Application ID” field, enter the “TruSales Application ID” from the “Required Setup Application User” step in the TruSales login process and select “SAVE” in the action bar.

Note: You will encounter an “Azure application ID not found” error if you have not accepted the application permission request in the initial TruSales login process. Please use the invitation URL provided by your Primary Intelligence implementation specialist to follow the initial login process until you have reached the “Required Setup Application User” step.

dyn12.png

Navigate to Manage Roles
Now that the Application User has been created, select “MANAGE ROLES” in the action bar to give it a security role.

dyn13.png

Assign TruSales Security Role
Select the “TruSales Application User” security role from the role list and select “OK” to assign the security role to your TruSales application user.

Note: If you did not import the “TruSales Security Roles” solution you can manually add the necessary permissions TruSales needs. Follow the “Application User Permission Requirements” section below to create a custom security role for your application user.

dyn14.png

 

Application User Permission Requirements

Your TruSales application user will need the following “read” permissions:

  • Account
  • Activity
  • Connection
  • Connection Role
  • Contact
  • Opportunity
  • Opportunity Relationship
  • Relationship Role
  • Competitor
  • Product
  • Currency
  • Organization
  • Security Role
  • User
  • Entity
  • Field
  • Relationship

And the following create permissions:

  • Connection
  • Contact

And the following miscellaneous privileges:

  • View Audit History
  • View Audit Summary

 

Required MS Dynamics Fields for Integration & Automation

Entity Required Fields
Opportunity
  • Opportunity (opportunityid)
  • Topic (name)
  • Description (description)
  • Sales Stage (salesstage)
  • Status (statecode)
  • Order Type (msdyn_ordertype)
  • Status Reason (statuscode)
  • Est. Close Date (estimatedclosedate)
  • Actual Close Date (actualclosedate)
  • Est. Revenue (Base) (estimatedvalue_base)
  • Actual Revenue (Base) (actualvalue_base)
  • Forecast Category (msdyn_forecastcategory)
  • Pipeline Phase (stepname)
  • Created On (createdon)
  • Modified On (modifiedon)
  • Owner (_ownerid_value)
  • Potential Customer (_accountid_value)
  • Account (_parentaccountid_value)
  • Created By (_createdby_value)
  • Modified By (_modifedby_value)
  • Contact (_parentcontactid_value)
  • (product_opportunities)
  • (opportunity_connections1)
Account
  • Account (accountid)
  • Account Name (name)
  • Owner ID (_ownerid_value)
  • Website (websiteurl)
  • Parent Account ID (_parentaccountid_value)
  • Relationship Type (customertypecode)
  • Record Created On (createdon)
  • Modified On (modifiedon)
  • Main Phone (telephone1)
  • Other Phone (telephone2)
  • Telephone 3 (telephone3)
  • Number of Employees (numberofemployees)
  • Annual Revenue (base) (revenue_base)
  • Ownership (ownershipcode)
  • Industry (industrycode)
  • Address 1: City (address1_city)
  • Address 1: Country/Region (address1_country)
  • Address 1: ZIP/Postal Code (address1_postalcode)
  • Address 1: State/Province (address1_stateorprovince)
  • Address 1: Street 1 (address1_line1)
  • (opportunity_parent_account)
SystemUser /azure/identity.js getUserInfo() does not specify properties, might retrieve all
  • User (systemuserid)
  • User Name (domainname)
  • Full Name (fullname)
  • Nickname (nickname)
  • Primary Email (internalemailaddress)
  • First Name (firstname)
  • Last Name (lastname)
  • Organization (organizationid)
  • Status (isdisabled)
  • Photo URL (photourl)
  • Title (title)
  • User Licensed (islicensed)
  • Main Phone (address1_telephone1)
  • Other Phone (address1_telephone2)
  • City (address1_city)
  • State/Province (address1_stateorprovince)
  • Country/Region (address1_country)
  • (entityimage_url)
  • Created On (createdon)
  • Modified On (modifiedon)
Role
  • Role (roleid)
  • Name (name)
  • Parent Role (_parentroleid_value)
  • Created On (createdon)
  • Modified On (modifiedon)
Organization
  • Internal Version (internalversion)
  • Base Currency Symbol (basecurrencysymbol)
  • Disabled Reason (disabledreason)
  • Audit Retention Period Settings (auditretentionperiod)
  • Audit Retention Period Settings (auditretentionperiodv2)
  • Is Audit Enabled (isauditenabled)
  • Organization (organizationid)
  • Name of the default app (defaultcrmcustomname)
  • Organization Name (name)
  • Created On (createdon)
Product
  • Product (productid)
  • Name (name)
  • Description (description)
  • Status Reason (statuscode)
  • Product ID (productnumber)
  • List Price (Base) (price_base)
  • Product Type (producttypecode)
Contact
  • Contact (contactid)
  • Account (_accountid_value)
  • Company Name (_parentcustomerid_value)
  • Owner (_ownerid_value)
  • Department (department)
  • Description (description)
  • Created On (createdon)
  • Email (emailaddress1)
  • First Name (firstname)
  • Last Name (lastname)
  • Full Name (fullname)
  • Address 1: City (address1_city)
  • Address 1: Country/Region (address1_country)
  • Address 1: Street 1 (address1_line1)
  • Address 1: ZIP/Postal Code (address1_postalcode)
  • Business Phone (telephone1)
  • Salutation (salutation)
  • Job Title (jobtitle)
  • Do not allow Phone Calls (donotphone)
  • Do not allow Emails (donotemail)
  • Mobile Phone (mobilephone)
  • Business Phone (telephone1)
Opportunity Product
  • Existing Product (_productid_value)
  • Quantity (quantity)
  • Extended Amount (Base) (extendedamount_base)
  • (totallineitemamount_base)
Connection
  • Connection (connectionid)
  • Connected To (_record2id_value)
  • Role (To) (_record2roleid_value)
Transaction Currency Currency Code (isocurrencycode)
Competitor
  • Competitor (competitorid)
  • Name (name)
  • Strengths (strengths)
  • Weaknesses (weaknesses)
  • Created On (createdon)
  • (opportunitycompetitors_association)
Opportunity Competitors (opportunityid)
Entity Definition
  • (logicalname)
  • (logicalcollectionname)
  • (displayname)
  • (primarynameattribute)
  • (primaryidattribute)
  • (iscustomentity)
  • (description)
  • (isauditenabled)
  • (schemaname)
Audit (_objectid_value)

 

 

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request