This post gives you guide on how to move your Dynamics Telephony configuration from one CRM to another.
The example is for porting from CRM1 (where you have tested everything to your satisfaction) to CRM2 (where you want to replicate the tested settings)
FIRST run Dynamics Telephony on CRM2. You do this by clearing the cache ( see here ) and starting Dynamics Telephony again. You will be prompted for the URL of CRM2. This will install the Dynamics Telephony solution in CRM2. IMPORTANT, once up and running, manually set items in Menu > Settings > Crm Configuration, as these cannot be ported over in the “Port Data” described below. Quit that instance of Dynamics Telephony.
THEN, Port Data between the Dynamis Telephony entities in CRM as follows…
CRM entity dialerKvTable – Delete all rows from CRM2 where scope equals global. Export all rows from CRM1 where scope equals global and import into CRM2
CRM entity dialerCallOutcome – Delete all rows from CRM2. Export all rows from CRM1 and import to CRM2.
CRM entity dialerDnis – You will have to manually re-create all DNIS Settings in CRM2. This is because the CRM URL is part of the DNIS definition. Also, the images for the DNIS are stored as webresources in CRM – which have the same name as the DNIS. Advanced users could manually fix the URL in the DNIS definition and port over the image webresources in a solution.
CRM entity dialerQueueSettings – You will have to manually re-create the Queue Settings on CRM2. This is because the CRM URL and the queue GUID is part of the Queue Settings.
CRM entity dialerReports – If you have made any custom report definitions for the Dynamics Telephony RTD, then you can port these to CRM2. Delete all rows from CRM2. Exports all rows from CRM1 and import to CRM2
You can easily add columns to the Agent RTD. The steps below show you how to add a total “Calls” column.
1.In Advanced Find, go to DiallerReports, use any view you like and click Results.
2. Then you click New DiallerReports
3. Here you click on the dashed lines to set/change the properties
For example, if you wanted to add a ‘Total Calls’ report, you could set it up like this.
Description is what will appear at the top of the column when in a table.
Key is the source of the data to be displayed.
Type is the data type. Here it is attribute. Other types include rule, filter, calculated and livestate. These will be discussed in another post.
Value is the column width in percent for attributes. For other types in can be different.
Order is the order in which the columns will appear. If you want to put a new column in the middle, the following columns will have to be manually shuffled forward.
ReportName is the report into which the column will be put.
Name is the name which can be used to cite this data in another report.
4. If you want to change the fields available, click form editor and drag fields from the right toolbar into the column on the left to add them in, or out of the left column to remove them
You can set the language to use for spellcheck within Dynamics Telephony. This would be used, for example, when composing an email in Dynamics Telephony. You can set it to one or multiple languages.
Use this for UK English
Use this for Spanish
This for US English
Or this for both US English and Spanish
Dynamics Telephony stores all its settings in CRM. Some are global and some are per user. You can change a user setting and make it global. This will mean that any new users will pick up that global setting as their default setting.
You might use this to, for example, make all new users use a particular telephony connector, when they first run. This would eliminate a manual configuration step that the user might get wrong.
In the following procedure, I will show you how to make a global setting that will default new users to use TAPI. The procedure is the same for other settings.
Set up Dynamics Telephony for one user and set their telephony to TAPI and their TAPI version to 2.1.
Close the Dynamics Telephony application
Run an Advanced Find in CRM on DialerKvTable to find the setting below
Change the “scope” value to “global”, per this snap.
Install a new user and they will default to TAPI 2.1
Dynamics Telephony supports a number of client rollout options to make the experience trouble free for all organization sizes.
All Dynamics Telephony settings are stored in CRM. This means you can pre-configure all users telephony settings. This can apply to any of the install options below. The items you would pre-configure are:
- All users default telephony (e.g. TAPI, Skype for Business, etc. )
- Individual user’s preferred telephony
- Telephony setting such as server, username and password
- Colors and preferences.
1. Install as click-once from Dynamics Telephony servers
This install can be done by end-users. the steps are
- Go to the install URL (that you would include in the instructions email)
- Download and run the setup.exe (If there might be security prompts in your environment, these should be dealt with in your instructions email)
- When prompted, enter the URL of the CRM (that you would also include in the instructions email)
- When Dynamics Telephony starts, go to Menu > Settings and pick your telephony provider from the list. For TAPI and Skype for Business, no further settings are required. For others, a username and password are required. NOTE you can also pre-configure all user’s settings in CRM to eliminate this step 4 completely. See GLOBAL SETTING above
We will help with defining this rollout procedure during the on-boarding process.
2. Install as click-once from your own server
Dynamics Telephony can provide you with the click-once install files for you to host on your own server. The install procedure would be the same as above. Advantages include:
- No dependence on the internet-based Dynamics Telephony servers
- Ability to prevent update rollout until you have verified compatibility with your needs.
Contact us for more information on this service.
Install from MSI
Dynamics Telephony can provide you with an MSI customized to your organization’s needs. Advantages include:
- Enables a completely silent install with no intervention from the user or IT.
- Specify the CRM URL for the user to use – normally this is entered by the user. With an MSI, this can be pre-configured.
- All other settings, such as the users telephony settings, can be pre-configured too per GLOBAL SETTINGS above.
- Customize aspects of the install such as application location, additional help files, shared phone-book location.
- Ability to prevent update rollout until you have verified compatibility with your needs.
- Additional customizations such as registry entries to simplify telephony driver install.
Please contact us for more information on this service.
Dynamics Telephony uses a CRM User we call the Service User. Dynamics Telephony uses the Service User in the background for various install and config tasks. The Service User has sysadmin role in CRM. You should restrict the permissions once the initial install is done.
The best practice for the Service User is to set up a dedicated user with a very strong password that never changes.
If you want to use an existing user as the Service User then you should use 2-factor authentication for this user, and use an App password per this Microsoft article here. With this approach you can change the user password without affecting the App Password.
If you need to change the Service User password, then it is best to change it in Dynamics Telephony at the same time as you do it in 365. Have one Dynamics Telephony client open at… > Settings cog > Settings > CRM Configuration. Then make the change in both places and restart all Dynamics Telephony clients.
If you change the password and get locked out of Dynamics Telephony, then follow the procedure below.
YOU ONLY HAVE TO DO THIS ON ONE PC
- Find dynamicstelephony.exe It is in a folder like:
- Right-click on the EXE and make a shortcut
- Edit the shortcut and add “/admin” at the end like this
Now, when you run Dynamics Telephony using this shortcut, and the connection to CRM fails, you will a the dialog where you can change the service user and password.
You probably want to restrict what settings and controls normal users can see in Dynamics Telephony.
To do this, you must add some security roles in CRM as detailed below. If you do not add these roles and assign them to certain users, then all users will have full access.
Dynamics Telephony uses 2 CRM roles to enable security features.
NOTE: These roles just need to exist. They do not need any permissions assigned.
ROLE: Dynamics Telephony Admin, when assigned to a CRM user will enable the “Admin Only Access” settings area for that user. Use this area to restrict other CRM users from seeing various settings.
For full lockdown you might restrict all but Log File and Provider Account (to allow telephony re-configuration)
ROLE:Dynamics Telephony Uninstall, when assigned to a CRM user will enable the “Uninstall” button in Dynamics Telephony for that user. “Uninstall” will completely remove the Dynamics Telephony Solution from CRM.
The best is not to assign this role to any user until you need it.
Dynamics Telephony policy is to have as little impact on your CRM as possible. Here are the impacts you need to consider.
As part of or submission to the Microsoft AppSource Store, install and basic tests were carried out by Microsoft Engineers.
Admin Level User will be required during the install phase. This is to allow for the installation of the entities described later. This user needs to be allowed install a solution in your CRM.
Authentication. Dynamics Telephony supports all authentication methods supported by CRM online or on-premises. When users use Dynamics Telephony, they simply logon to CRM as normal.
HTTPS and HTTP are both supported. The certificate for HTTPS needs to be trusted by Internet Explorer.
Install procedure is described HERE
Entities Installed by Dynamics Telephony are listed HERE. The entities are all standalone with no dependency in your standard entities on the Dynamics Telephony entities. They are installed as a solution that you can request to inspect. They can be uninstalled with no impact on your CRM.
Entities written by dynamics Telephony:
– Dynamics Telephony entity records.
– Phonecall due to click-to-dial or incoming calls.
– Note due to click-to-dial or incoming calls.
– (optional) create contact for unknown caller.
These records are written using the logged-on user. See relationships below:
The following entities are installed in your CRM by Dynamics Telephony for its own use. They are stand-alone entities that can be uninstalled without affecting your own data.
- DialerCall – every call made or received
- DialerCallEvent – every telephony event (dial, answer, etc.)
- DialerCallResult – every reported Outcome
- DialerCallOutcome – Outcome buttons configuration
- DialerDNIS – configure inbound lines
- DialerUser – realtime user status for RTD
- DialerKV – Global and per user settings
- dtThisWeek, month, day, year dashboards – Dashboards to display statistics
- dtRTD – web resource to display agent realtime status