Migrating Data into Intake Forms with Grids

This topic describes the items to consider when migrating legacy transaction data into intake forms with grids.

Overview

The information in this topic applies to agencies using the Oracle Fusion Import Management tool to migrate legacy data from a source system into the Oracle Permitting and Licensing system. In particular, this information will help guide you to migrate data from a legacy object, such as a permit or business license, into your new Oracle Permitting and Licensing intake form, where some of the data is stored and represented in a grid. For more information on intake form grids, see Working with Grids.

It is assumed that you have:

Created and published the target intake form in the Oracle Permitting and Licensing system.
Completed analysis of the source and target objects and know the required data mappings to the target objects.

It is important to consider the structure of the intake form as it's reflected in the Oracle Permitting and Licensing database. The intake form itself is the parent object, and any grid associated with that intake form object is a child object of the intake form object. When importing data into an intake form object, migrate:

Each object (intake form, parent, child, and so on) individually.
Parent objects before child objects.

Migrating Intake Form Parent Data

First, you'll need to set up the import CSV file for the parent record.

Import Management > Import Objects.
Search for the display name of your intake form object.
Make note of the required attributes and key attributes.
Click Download to create CSV template file.
Update the template with values for required fields.

Update these attributes as described:

Attribute	Considerations
LnpRecordKey	This should be blank. This value should be automatically generated within Oracle. If you provide a value, the import will perform an update instead of an insert.
Rowtype	Add the intake ID, such as `LNP1RMODATAIMPORTGRID_c`
LayoutVersion	Not marked required but needed for data import processing. If using the versioning feature, an intake form can have multiple versions, such as V1, V2, or whatever your versioning syntax is. If not using the versioning feature, enter `V1`. For more information on versioning intake forms, see Creating Intake Form Versions.

Attribute

Considerations

LnpRecordKey

This should be blank. This value should be automatically generated within Oracle. If you provide a value, the import will perform an update instead of an insert.

Rowtype

Add the intake ID, such as LNP1RMODATAIMPORTGRID_c

LayoutVersion

Not marked required but needed for data import processing. If using the versioning feature, an intake form can have multiple versions, such as V1, V2, or whatever your versioning syntax is. If not using the versioning feature, enter V1.

For more information on versioning intake forms, see Creating Intake Form Versions.

Within Import Management navigate to Import Queue > Create Import Activity, and modify the following:
1. Name: Add a job name.
2. Object: Search and select your migration object.
3. File Name: Select your generated CSV file.
4. Click Next as needed.
5. It is recommended to validate data.
6. Click Submit.
7. When the job finishes, check for and resolve any errors.

Migrating Intake Form Grid Child Data

After the parent intake form object has been migrated, then you can migrate the child grid data.

Import Management > Import Objects.
Search for the display name of the intake form grid object.
Make note of the required attributes and key attributes.
Click Download to create CSV template file.
Update the template with values for required fields.

Update these attributes as described:

Attribute	Considerations
GridKey	This should be blank. This value should be automatically generated within Oracle. If you provide a value, the import will perform an update instead of an insert.
Parent Record Identifier	You'll see a column in the CSV representing the intake form object and grid, such as `LNP1RMODATAIMPORTGRID_rel_LNP1RMODATAIMPORTGRIDg1_LNP1RMODATAIMPORTGRID_Id_c` The value is the LnpRecordKey in the parent object, such as 300100634725835.

Attribute

Considerations

GridKey

This should be blank. This value should be automatically generated within Oracle. If you provide a value, the import will perform an update instead of an insert.

Parent Record Identifier

You'll see a column in the CSV representing the intake form object and grid, such as LNP1RMODATAIMPORTGRID_rel_LNP1RMODATAIMPORTGRIDg1_LNP1RMODATAIMPORTGRID_Id_c

The value is the LnpRecordKey in the parent object, such as 300100634725835.

Within Import Management navigate to Import Queue > Create Import Activity, and modify the following:
1. Name: Add a job name.
2. Object: Search and select your migration object.
3. File Name: Select your generated CSV file.
4. Click Next as needed.
5. It is recommended to validate data.
6. Click Submit.
7. When the job finishes, check for and resolve any errors.

Verifying the Migration

To verify the migrated data, go to the transaction details for the offering type, such as Permit Details, License Details and so on.

Open the intake form and verify the migrated data is appearing as expected.