The table in an upgraded Enterprise geodatabase matches an existing property table in a Workflow Manager repository

Description

If a one-to-one extended property table is imported to a Workflow Manager repository, for which the owner name and table name match an existing table in an upgraded Enterprise geodatabase, Workflow Manager treats it as two, separate tables. However, a conflict can occur if both tables are configured to the same job type, which causes the following error to display when the user creates a job using the job template:

Error
Extended (one-to-one) properties already exist for this job.

Cause

Starting at version 11.0, Enterprise geodatabase system tables no longer store the database name as part of the fully qualified name in ArcGIS applications. For example, dbname.ownername.tablename becomes ownername.tablename.

Solution or Workaround

If a table in an upgraded Enterprise geodatabase matches an existing one-to-one extended property table in a Workflow Manager repository, restore the Workflow Manager configuration by removing the duplicated extended property table.

1. Upgrade your Enterprise geodatabase from version 10.9.1 to 11.x.
2. If a table is imported after an 11.0 Enterprise geodatabase upgrade, the table no longer includes the database name as part of the fully qualified name.
3. Note any tables for which the new fully qualified name matches that of an existing one-to-one extended property table in your Workflow Manager repository.
4. To avoid conflict, do not configure extended property tables with matching fully qualified names to the same job type.
5. If you receive the extended properties error when creating a job, check the job type for duplicated extended property tables.
   • If duplication exists, remove the older extended property table.