If you are mapping text fields into codes, or, if you have any other data that need to be converted during the import, create the necessary correlations.
Email Tab
Fill out the information on this tab if you want Lucity to send out an email notification when the import is complete.
If you are mapping text fields into codes, or, if there are any other data that need to be converted during the import, create correlations.
Email Tab
Complete these fields if you would like the system to send out an email notification when the import is complete.
Click to save the configuration.
Repeat Steps 1-8 to create configurations for each element of the Group Import.
Notes: On the General Tab, the Group Name must be the same for all configurations. The Group Order value must be different for each element of the Group Import.
If your import records include information about documents or pictures that should be attached to the imported/updated record you can update Lucity with a link to that file.
Important: The import and Update does not upload the file to Lucity's Document Hive. The import will only add a link to the file's existing location. You must place the files in the desired storage location and point Lucity to these files for the system to operate.
On the Mapping Tab create mappings for the following information
Document Description - A required description for the document. This can be the file name.
Document Path - The entire path to the document including the filename and extension. If the document is stored in a location that the Lucity Document Server has access to it will be able to serve the document to web and mobile users.
Document is a Web Page - Flag this if the document is actually a web url.
Document Open Directly- Marks whether the Lucity Document Server should attempt to open the file, or give the user a path, when a user attempts to open the document. Usually used for large files.
Document Publicly Available - Flag documents that are attached to Work Requests to control if the document will be available via the Lucity Citizen Portal RESTAPI.
Document Copy to Work Order - Flags a document attached to a record. When a work order is created from that record the document will be attached to the work order.
Open the Import and Update tool and click the drop down arrow next to the . Select Add Template.
The following pop-up will appear:
Select one or more templates from the list.
Note: Most Lucity provided templates are part of a group. You will need to load and edit every template in that group.
Click Load.
The selected template(s) will be added into the import and update tool.
For each loaded template, edit the Template, change the Name so that it is unique and does not match the original template name and press Save. This is necessary before making any additional changes to the loaded Template(s) so that they are initially saved to the Lucity database.
Each template is as filled out as much as possible. You will need to provide the following
General Tab > Output Directory - The location that you want bad records exported to.
Data Source Tab > Data Source - Point this to your import database.
Click to save the configuration.
When the save is successful the following pop-up will appear:
Click the Yes button all the other templates in this group use the same Data Source.
Go to each other template you imported and click .
Click the button on the toolbar to export all configurations. Skip to step 4.
OR
Click the drop-down next to the button on the toolbar and select Export Selected Configurations to pick one or more configurations from a list. The following pop-up appears.
Select one or more configurations from the list.
Click Export.
The save pop-up will appear. Select a location and set a file name as desired.
Click Save.
A single XML file will be exported with the desired configurations.
Indicates the program should run silently, without displaying forms or error messages.
/P
Indicates the path for the setup file(s) and the default locations of objects. This portion of the script is required only if the Lucity.ImportAndUpdate.exe file was moved to a new location. If the file was moved, this parameter should point to the original location where all the accompanying files are still stored.
Path
Indicates the path to the Setup file.
Note: If there is a space in this value you must start and end the value with " ".
Specifies which saved import configuration to run.
Configuration *
The name of the configuration.
Note: If there is a space in this value you must start and end the value with " ".
Example: /L"Hydrant Inspection Import"
/C
Indicates the Lucity client.
Client
The system ID of the Lucity client. This will be something like clint001 or clint002.
You can find this in Client Maintenance by selecting the client from the installed client list and looking at the value in the Associated Client field.
/G
Indicates that if the configuration is part of a group, the configurations with a greater order should also run.
After configuring your import use the following steps to schedule the import.
Login the server that is running the Lucity Services. The windows credentials you use must be mapped to a Lucity login that has permission to make updates to the modules that this Lucity Import configuration will be updating
Locate and run the Lucity.ImportandUpdate.exe. This is typically located in the C:\Programs FIles (x86)\Lucity Services directory.
Login using windows authentication.
Select your import configuration. If it is part of a grouped import select the first configuration for the group.
Click the on the toolbar. The following pop-up will appear:
Enter a Name for the schedule.
If desired you can change the Lucity user the program Runs As. By default it runs as the services user.
Note that if you change this user you must make sure they have the necessary permissions to add/update records in the target module. You also need to make sure that a license is available for the module you are importing into.
Make sure the Enabled box is checked.
Note: Currently the Lucity Scheduler only supports running once a Day at a specific time or every few minutes. Other sections of the form are disabled.
Use the Frequency section to set which days the import will run on.
Use the Occurs dropdown to select whether the import will run Daily or Weekly.
Use the Recurs Every field to set how many days should pass between when the import runs.
If Weekly is selected use the checkboxes to mark which days of the week the import should run.
Use the Daily frequency section to determine what time the import runs on the days that it is set to run.
To run once at a set time click the Occurs once at: button and select the time the import will run at..
To run all day on a time interval:
Click the Occurs every: button.
Select whether the import will be happeing at an interval of Hours or Minutes.
Select the number of minutes between times that the service will run.
Set the Starting at time and Ending at time. The schedule will only run between the indicated times on the appointed day..
Set a Duration.
Set a Start Date. The import will start running on that date. It will automatically be set to the current date.
If desired set and End Date. The import will stop running on that date.
Click OK.
Save the changes to the import configuration.
Example: In the below example the import will run every day, and will run every 5 minutes between 2 am and midnight. It will start this schedule on August 21, 2018, and will never stop on its own.
On the General tab check the Track Processed Records box.
On the Mapping tab map some data to the TrackingIdentifier field. It should be mapped to a field that uniquely identifies the record.
Ideally this is the same field you used for the Common ID
This may include a formula that builds a unique tracking ID based on one or more fields from the import data. (ex. Asset ID + Inspection Date for an inspection)
These records will now appear on the Processed tab.
Make sure that you use the Common ID used in your data source to map to the TrackingIdentifier field.
If you are using Microsoft Access you will need open the database and link in the CMIMPPROCESSED table from the SQL database.
If you are using Microsoft SQL server your databases will need to be in the same sql instance.
Go to the Data Source tab
Update your Data Select SQL to exclude records that overlap with the Lucity.CMIMPPROCESSED table.
Example: SELECT * FROM DATASOURCE WHERE DATASOURCE_ID IS NOT NULL AND DATASOURCE_ID NOT IN (SELECT PRC_UNIQUE_ID FROM Lucity.dbo.CMIMPPROCESSED INNER JOIN Lucity.dbo.CMIMPORTUPDATE ON IMP_ID = PRC_IMP_ID WHERE IMP_NAME = 'Your Import Name')
Make sure that you use the Common ID used in your data source to map to the TrackingIdentifier field.
On the Mapping tab find the SkipProcessingIfNotBlank field.
Add the following formula
+SELECT TOP 1 PRC_ID FROM CMIMPPROCESSED INNER JOIN CMIMPORTUPDATE ON IMP_ID = PRC_IMP_ID WHERE IMP_NAME = 'Your Import Name' AND PRC_UNIQUE_ID = '=A12'
Replace the Your Import Name with the Name field for your Import Configuration.
Replace the =A12 with the field or formula you used to map the TrackingIdentifier field.
When running the import the will check each record to see if there is a matching record in the processed tracking table. If there is it will skip that record. If there isn't the record will be processed.