Migrating from an old import program.

Jonathan Semones -

The Import and Update program is a powerful program that allows for both importing new records and updating existing records within Lucity from an external data source. It is taking the place of Lucity's older import programs. To continue importing your data you need to need to move you existing import configurations from the old Lucity Import program into the Import and Update program. While this is a manual process it is a good chance to review the data you are importing and make any desired changes.


Custom Import Configurations
These are general imports you setup in the old Lucity Import program. Use the following steps to move them over.

  • Find a sample of the data that you are trying to import.
  • Open the old Lucity Import and load a saved import mapping.
    • On your machine go to C:\Program Files (x86)\Lucity\bin and launch the LucityImport.exe.  The following pop-up will appear:

    • Enter your Lucity login in the User field.
    • Select which Client you had the import configured for.
    • Select which Database the data would have been stored in.
    • Click OK.
    • The import tool will open.

    • Use the ... button next to the ASCII File field to select your Sample data.
    • Choose what it is Delimited By.
    • Select the module the data is imported into in the Destination Table.
    • The Saved Settings grid will now display your configured imports.
    • Select a saved setting and click Mapping.
  • Open the Import and Update program and add a new import configuration.
    • In Lucity Desktop go to General > Import and Update.
    • Click  to create a new configuration.
    • Enter the Import Name.
    • Use the General Tab to select the part of the Lucity program into which the records will be imported.
    • Use the Data Source Tab to select your Sample data.
    • Click on the Mapping Tab.
  • Compare the mapping screens from the two imports.
    • In the Import and Update tool find the data you want to import and map it to the field it should go into.
    • For the majority of fields these mappings will be the same in both systems. As in the example above.

Mapping Exceptions

The old Lucity Import program loaded data directly into the database. It didn't take into account the rules and automatic functionality that is built into Lucity. The import and update program loads data into the database through Lucity's business object framework which takes into account all of Lucity's rules and automatic functionality.

Properties

  • To use the Lucity business object framework the Import and Update map data to properties instead of fields. Properties are things like Inspection Date, or Alternate ID, or Street Name. These properties then represent fields withing Lucity. Most properties have a 1 to 1 relationship with a field. So the Status property for a module links to a Status field for the module.

Exception

  • Some properties represent a group of fields. The street name for a record is stored in five different fields but there is only one property.In this situation if your import data has the street name broken out into multiple fields you will need to use a formula to map all those fields to the single property.

Example: +'=A1' + CASE WHEN '=A2' <> '' THEN (' =A2') END + CASE WHEN '=A3' <> '' THEN ' =A3' END

Required fields

  • Most records in Lucity have some sort of required fields. These fields must be filled out before a record can be successfully imported.

Exception

  • Some of these are required by the database and are automatically populated when you add the record through one of the Lucity programs. Examples would be the Last Modified By, Last Modified Date, and Last Modified Time fields. Since the old Lucity Import program didn't take into account Lucity's automatic functionality these fields had to calculated in the mapping. The Import and Update calculates these fields automatically so they do not appear in the mapping.

 

Lucity Configured Imports
These are imports for specific modules that follow some sort of special or standardized pattern. These imports are often consist of multiple imports that are run as a group. Example Sewer TV or PACP imports. Use the following steps to implement these.

Note: If there are not specific instructions for the way you import your data please contact Lucity Support.

IT Pipes > Sewer TV Inspections module

  • Find a sample of the data that you are trying to import.
  • Create your import configurations from the ITPipes templates
    • 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 the IT Pipe Sewer... templates from the list.
    • Click Load.
    • The selected template(s) will be added into the import and update tool.
    • On the General Tab fill out the Output Directory with the location that you want bad records exported to.
    • On the Data Source Tab fill out the Data Source with the path to your sample ITPipes 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 .
  • Update your mappings and correlations
    • Check the Mappings tab for each ITPipes configuration.
    • Make sure that the import data is being imported into the fields that you want inside of Lucity.
    • If your ITPipe defects/observations match your Lucity defects/observations then you are done.
    • If your ITPipe defects/observations do not match your Lucity defects/observations you will need to do further configuration.
    • On the ITPipe Sewer Pipe TV Inspection Observations tab go to the Correlations tab.
      Each ITPipe defect must have a record in this table.

    • When you are done make sure to save the changes.

NAASCO PACP > PACP Inspection modules

  1. Find a sample of the data that you are trying to import.
  2. Create and configure your import configurations from the PACP templates.
    • 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 the NASSCO PACP... templates from the list.
    • Click Load.
    • The selected template(s) will be added into the import and update tool.
    • On the General Tab fill out the Output Directory with the location that you want bad records exported to.
    • On the Data Source Tab fill out the Data Source with the path to your sample PACP 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 .

 

NAASCO MACP > MACP Inspection module

  1. Find a sample of the data that you are trying to import.
  2. Create you import configurations from the MACP templates.
    • 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 the NASSCO MACP... templates from the list.
    • Click Load.
    • The selected template(s) will be added into the import and update tool.
    • On the General Tab fill out the Output Directory with the location that you want bad records exported to.
    • On the Data Source Tab fill out the Data Source with the path to your sample MACP 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 .

 

Have more questions? Submit a request

Comments