Warning: This document contains instructions for adjusting app synchronization settings that can adversely affect your device data, user data, and/or user mapping settings in Incident IQ. As such, only qualified personnel should proceed with making adjustments to the settings outlined in this document.
The following guide is designed to give district administrators an overview of the following topics:
- A step-by-step guide on integrating an on-premise (non-cloud) version of a Destiny integration with Incident IQ
You can use the following links below to quickly navigate to a specific section in this document. To quickly return to this index, use the "Return to Index" link located at the end of any section.
- Setting up the SQL Database
- Configuring and Downloading the Destiny Executable File
- Setting up a Nightly Sync
- Setting up Automated Asset Creation
Setting up the SQL Database
To install the Destiny on-premise integration app you will need to start off by connecting to the Destiny database in SQL Management Studio. Once connected, you will want to right-click on the SQL server in the Object Explorer tree and select Properties.
In the Select a Page menu, click on the Security page.
Under Server Authentication click on SQL Server and Windows Authentication mode (if this is not already selected). Click OK.
The SQL service will need to restart if changes were made. This is done by right-clicking the SQL server node, and clicking Restart. Click OK and, if the SQL Server Agent service is running, you will also need to click OK to confirm it too should be restarted as well.
In the Object Explorer tree, expand the Security folder, right-click the Logins folder and click New Login.
Select SQL Server Authentication, provide a Login name, a password, and uncheck the Enforce password policy option.
In the Select a Page menu, click on User Mapping. Locate the Destiny database in the primary list, and check the checkbox in the Map column next to it. In the Database role membership-list, click the db_datareader. Click OK.
Configuring and Downloading the Destiny Executable File
You will now need to configure and download the executable file for the Destiny app to a local machine with access to your SQL server that runs overnight. To do so, begin by selecting Manage on the left navigation bar.
Important Note: If the Destiny App has not been installed yet, you should select Browse instead and install the app. After app installation is completed, you may access this app from the Manage menu.
This will take you to your Installed Apps page where you can select the Options button to access the Destiny app management.
From here, click on the Sync Executable tab in the Destiny app.
In the Sync Executable tab, begin by selecting the Default SQL Command Template to load based on the current version of your SQL server.
You will now need to identify the following portion of the template code to edit your device categories information:
[t].Level2ID IN (
156, -- Audio Visual
157, --Business Machines
160, --Computer Equipment
168, --Video Equipment
184, --Networking Equipment
206, --Software Media
302 --Classroom Equipment
--1211 --CTAE Misc.
To identify your device categories you will need to run the following query on the Destiny SQL server:
SELECT * FROM [CircCatAdmin].[AssetTemplate]
After you have run the query and identified the list of your categories you will need to delete the category information from the template code in the Destiny integration until you are left with the following:
[t].Level2ID IN (
Now you will want to copy and paste the category codes separated by commas into the SQL template at which point your code will look similar to the following:
[t].Level2ID IN (
1, 100, 101, 102
Once you have completed editing the predefined template, you will now need to enter the following information in the Database Connection Settings:
- Server Name/IP
- Database Name
- Page Size
After these fields have been filled out, click on Download Executable. As mentioned earlier, this executable will need to be downloaded to a machine with access to your SQL server that is left on overnight. Once downloaded, you will then need to run a manual sync of the app to ensure that all settings have been configured properly.
Setting up a Nightly Sync
To schedule the sync to occur automatically, you'll need to create a task in Windows Task Manager. You can do so by searching for Administrative Tools and selecting Task Scheduler. This will open the Task Scheduler window.
In the Task Scheduler window, start by clicking on Action > Create Basic Task...
This will open the Create Basic Task Wizard. At the very least, you will need to provide a name for the new task. You can also add a task if desired. Once this is completed, click Next.
In the next step, you will be asked to select when this task should Trigger. We recommend running it daily (overnight) for the most accurate user data. Please ensure that you set the task to run regardless of whether a user is logged in or not on the server. Once complete, click Next.
For the next step, you will need to specify what action the task will take when running. Select Start a Program and then click Next.
When specifying the action to perform, locate the file IncidentIQ.Connectors.LocalSQL.exe in the Program/script file browser. Supply the argument -service in the Add arguments field. And finally, you will need to indicate the path you unzipped the files too in the Start in field. Once complete, click Next.
In the final step, you may review all of the settings of your task. Once you have completed your review, check Open the Properties dialog for this task when I click Finish option and then click the Finish.
In the sync properties window, you will need to check Run whether user is logged on or not as well as Run with highest privileges. Click OK to complete the sync setup.
Setting up Automated Asset Creation
First, you will need to ensure that the Create Asset option is turned on. This is located in the in the General Settings tab of the app.
Next you will need to ensure that locations have been setup in the Locations Tab. Please keep in mind that assets need to have a location when brought into the system. The way this works during a sync is as follows:
- If an asset matches a custom mapping, then the asset will get created and assigned to the corresponding location the mapping is set to.
- If an asset does not match a custom mapping, or no custom mappings are present, and a default location is selected, then the asset will get created and assigned to the default location.
- If an asset does not match a custom mapping, or no custom mappings are present, and there is no default location set, then the asset will not be created during a sync.
For additional details, please refer to the Locations Tab section of this document.
And finally, you will need to ensure that the particular model of the asset in mapped in the Model Mapping Tab.
Please note, when you first install your app this field will be blank. This is because Incident IQ has not yet run a sync to scan which models are stored in Destiny. To pull model information in, simply click on Run Sync in the General Settings Tab. Once completed, you should see a full list of all available models in your Destiny instance.