Users of ICONICS CFSWorX can define all of their workers in the local database using the default "Local-Default" worker source. Alternatively, the have the option of utilizing either a Microsoft Dynamics 365 or an Active Directory source to import a list of field workers from those systems.
To Add a Dynamics 365 Source
Expand your project in the Workbench, and then expand the Connected Field Worker node.
Right-click on the Field Workers branch, then select Add Dynamics 365 Source from the pulldown menu, as shown below.
Add Dynamics 365 Source from the Project Explorer
-OR-
Select the Field Workers branch in the Project Explorer then click on the Add Dynamics 365 Source button, shown below, in the Edit section of the Home ribbon in the Workbench.
Add Dynamics 365 Source Button
This opens the Field Workers - Dynamics 365 Source configuration window, as shown below, within the Workbench. Enter a name for this configuration in the Name text entry field.
Field Workers - Dynamics 365 Source Configuration
Settings
Enabled -True to enable this specific Field Workers - Dynamics 365 Configuration.
Source -This reflects the selected source type. In this example, Dynamics 365 has been selected.
Use Dataset Caching - When enabled, dataset query results will be cached temporarily. The cached information will be returned during the Caching Period if the same dataset is requested by any client.
Caching Period – this setting defines the length of time to retain the cached dataset. After this period passes, any subsequent request will require rebuilding the dataset values.
Dynamics 365 Settings
Before configuring the Dynamics 365 source in CFSWorX, please refer to Configuring Dynamics 365. You must configure the proper settings in Microsoft Azure and Dynamics 365. The AppID and Secret will be used in the steps below.
Dynamics 365 Instance URL -Enter the URL of your selected Dynamics 365 instance in the text entry field.
AppID - Enter the Application ID of your Azure App used to connect to Dynamics 365.
Secret - Enter the Client Secret of your Azure App used to connect to Dynamics 365.
Synchronization period -Enter the synchronization period (in minutes) in the text entry field (or use the up/down arrow buttons). This defines the frequency when workers, groups and related information will be synchronized with Dynamics 365. Click the Synchronize now button to manually trigger the synchronization. The operation will be executed asynchronously and a status message will show whether or not the request started successfully. Note that the status message will not provide information on whether the operation succeeds or fails at a later point (in that instance, users can check TraceWorX for full info).
Import Worker Images - If checked, worker images will be imported and saved on the server in the specified location.
Ignore Schedule Exceptions - If checked, then Breaks will not be considered when determining if the worker is scheduled or not. This may be useful if you still want to contact a worker while they are on break, but still on duty.
Only users from specific group(s) - Click HERE for more info on Enhanced Group Filtering in Dynamics 365 Sources.
Enabled - True to enable selection of import of users from specifically selected groups.
Import Resource Categories - If checked, import all workers belonging to the specified Resource Category (also known as a role). If defining a Specific value, then the organizational unit must match the name of a Resource Category defined in Dynamics 365. Enter the values in the text entry field or click on the 
to navigate to your selected Resource Category/Categories. Multiple Resource Categories may be specified by separating the names with commas. If All is selected, then all workers belonging to any Resource Category will be imported.
Import Organizational Units - If checked, import all workers belonging to the specified Organizational Unit. If defining a Specific value, then the Organizational Unit must match the name of a category defined in Dynamics 365. Enter the values in the text entry field or click on the to navigate to your selected resource Organizational Unit(s). Multiple Organizational Units may be specified by separating the names with commas. If All is selected, then all workers belonging to any Organizational Unit will be imported.
Import Characteristics - If checked, import all workers having the specified Characteristic. If defining a Specific value, then the Characteristic must match the name of a category defined in Dynamics 365. Enter the values in the text entry field or click on the to navigate to your selected resource Characteristic(s). Multiple Characteristics may be specified by separating the names with commas. If All is selected, then all workers having any Characteristic will be imported.
Import Business Units - If checked, import all workers having the specified Business Unit. If defining a Specific value, then the Business Unit must match the name of a category defined in Dynamics 365. Enter the values in the text entry field or click on the to navigate to your selected Business Unit(s). Multiple Business Units may be specified by separating the names with commas. If All is selected, then all workers belonging to any Business Unit will be imported.
Import Teams - If checked, import all workers having the specified Team. If defining a Specific value, then the Team must match the name of a category defined in Dynamics 365. Enter the values in the text entry field or click on the to navigate to your selected Team(s). Multiple Business Units may be specified by separating the names with commas. If All is selected, then all workers belonging to any Team will be imported.
Import Territories - If checked, import all workers having the specified Territory. If defining a Specific value, then the Territory must match the name of a category defined in Dynamics 365. Enter the values in the text entry field or click on the to navigate to your selected Territory/Territories. Multiple Territories may be specified by separating the names with commas. If All is selected, then all workers belonging to any Territory will be imported.
Note: When using any of the Specific options above, all names must be written with only letters, spaces, and numbers, removing all other characters. For example, “Company X, Inc.” should be written as “Company X Inc”.
Dynamics 365 Work Order Settings
The following options are used for creating work orders:
Service Account – This is the account to be serviced, as defined in Dynamics 365.
Billing Account – This is the account to be billed, as defined in Dynamics 365.
Price List – This is the price list that controls pricing for products and services related to this work order. By default, Dynamics will use the price list specified on the account.
Once you have completed setting your Field Workers - Dynamics 365 Configuration properties, click on Apply, then Close to return to the Workbench.
To Add an Active Directory Source
Expand your project in the Workbench, and then expand the Connected Field Worker node.
Right-click on the Field Workers branch, then select Add Active Directory Source from the pulldown menu, as shown below.
Add Active Directory Source from the Project Explorer
-OR-
Select the Field Workers branch in the Project Explorer then click on the Add Active Directory Source button in the Edit section of the Home ribbon in the Workbench.
Add Active Directory Source Button
This opens the Field Workers - Active Directory Source configuration window, as shown below, within the Workbench. Enter a name for this configuration in the Name text entry field.
Field Workers -Active Directory Source Configuration
Settings
Enabled -True to enable this specific Field Workers - Dynamics 365 Configuration.
Source -The pulldown menu should reflect your selected source. In this example, Active Directory has been selected.
Use Dataset Caching -Check this box to use worker dataset caching and reduce server load.
Caching Period - If "Use Dataset Caching" is selected, you can enter the caching period (in seconds) in the now active text entry field, or use the up/down arrow buttons.
Active Directory Settings
Domain Name – This is the domain name. Can be a long or short (Netbios) name.
Server Type:
Domain LDAP – With this option, our Security will connect to the default controller of the domain.
Global Catalog – Security will connect to the Global Catalog. A Global Catalog in Active Directory is a read only cache of all domains in a single domain forest. Use this option, users are in multiple domains inside a single forest, and the Security needs to show them all.
Map user name from - For users, Security will use the selected Active Directory attribute as the username. Users which do not have this attribute specified in Active Directory will not be shown.
SAM-Account-Name – This will use the “SAM-Account-Name” attribute.
User-Principal-Name – This will use the “User-Principal-Name” attribute.
AD synchronization period - Enter an Active Directory synchronization period, in minutes, in the text entry field. Click the Synchronize now button to manually trigger the synchronization. The operation will be executed asynchronously and a status message will show whether or not the request started successfully. Note that the status message will not provide information on whether the operation succeeds or fails at a later point (in that instance, users can check TraceWorX for full info).
Only users from a specific group
Enabled - Click this checkbox to allow log in only from a named group. Once checked, you can enter the group name in the setting below.
Group name - Enter a group name in the text entry field that will contain users allowed to log in.
Domain connection authentication
This section is all about securing the connection between our Security (running as an internal part of the FrameWorX Server) and the Active Directory.
User name - Enter a user name in the text entry field. If filled in, this will get used to authenticate access to the Active Directory, so that Workbench and Security can list users, groups and all it needs. If left empty, Security will try to authentication using the identity of the FrameWorX server process. This will work only if the FrameWorX server process is running under a domain account which has access to the Active Directory.
Password - Enter a password in the text entry field. If filled in, this will get used to authenticate access to the Active Directory, so that Workbench and Security can list users, groups and all it needs. If left empty, Security will try to authentication using the identity of the FrameWorX server process. This will work only if the FrameWorX server process is running under a domain account which has access to the Active Directory.
Authentication type - How the credentials are transferred to Active Directory for verification. These two setting correspond to the options “Secure” and “None” in this link: https://msdn.microsoft.com/en-us/library/system.directoryservices.authenticationtypes.aspx.
Secure – Security will use Kerberos, and possibly NTLM to authenticate to Active Directory. This is the recommended setting.
Basic (simple bind) – Security will use basic authentication
Use Secure Sockets Layer (SSL) - Security will use LDAPS (LDAP over SSL). This needs to be supported by the Active Directory, for details. Details to set this up are outside our concern.
Once you have completed setting your Field Workers - Active Directory Configuration properties, click on Apply, then Close to return to the Workbench.
See Also:
Enhanced Group Filtering in Dynamics 365 Sources