Migrating Form Design Data with Application Data Sets

You can migrate form design data using delivered Application Data Sets.

The following table lists the delivered ADS definitions (delivered in Data Set Designer) to support the migration of form design data:

Delivered ADS to Support Form Design Migration

Application Data Set (ADS) Usage

EOFM_FORM_DEFINITION

Select this dataset on the Data Migration Workbench to migrate form definition data from one database to another.

Only activated forms are available for selection in this ADS.

It moves data for the following tables:

  • FORM_TYPE

  • FORM_TYPE_LG

  • EOFM_FORMROLE

  • EOFM_REPORTROLE

  • EOFM_TILE_IMG

EOSD_RECDEFN

EOSD_RECDEFN dataset gets pulled automatically as Related Data Set with ADS EOFM_FORM_DEFINITION. This ADS should not be used independently.

It moves data for the following tables:

  • FS_SD_REC

  • FS_SD_REC_LG

  • FS_SD_RECFLD

  • FS_SD_RECFLD_LG

  • FS_SD_FLDCD

  • FS_SD_FLDCD_LG

  • FS_SD_FLDPC

EOSD_GRPDEFN

EOSD_GRPDEFN dataset gets pulled automatically as Related Data Set with ADS EOFM_FORM_DEFINITION. This ADS should not be used independently.

It moves data for the following tables:

  • FS_SD_GRP

  • FS_SD_GRP_LG

  • FS_SD_GRPFLD

  • FS_SD_GRPFLD_LG

EOFM_SD_PROMPT_REC

Select this dataset on the Data Migration Workbench to migrate Define Prompt Records setup from one database to another. This is required only if the form definition you are migrating uses prompt records.

It moves data for the following table: FS_SD_PROMT_REC.

  • Forms need to be activated in the target database after migration.

  • For activating a form, open the form in Form Designer and use Activate button/link.

  • For fluid Forms, Reporting View is created during activation if Reporting Role is present. Reporting View name is based on availability in target database and may be different from the source database.

  • A minimum tools release of 8.59 is required to support migration of form design data.