How to export Database enumeration values when creating new project area
Database enumeration values are stored in the Database.
If we create a new project area, based on on existing project area that is using DB enumeration values(Create a template from this project area and use it to create a new project area) then DB based enumeration values are lost in the new project area.
Is there a way to export the Database enumeration values to the new project area from an existing project area ?
If we create a new project area, based on on existing project area that is using DB enumeration values(Create a template from this project area and use it to create a new project area) then DB based enumeration values are lost in the new project area.
Is there a way to export the Database enumeration values to the new project area from an existing project area ?
2 answers
as U discovered database enums are not supported in shared projects.
there is no current way that I know of to export the list. and if there was an external source, no way that I know of to import that list into a recreation of the enum list in a new project area.
there is no current way that I know of to export the list. and if there was an external source, no way that I know of to import that list into a recreation of the enum list in a new project area.
Comments
I am seeing a defect where the definition of a Database enumeration is not being correctly exported into a process template export file that can be later imported into another RTC server.
I created a PA with a database enumeration. I then exported the process template and imported it into a new RTC server. I then created a project area on the new RTC server based on the imported template.
The problem is that the work items using the database enumeration are invalid.
The definitions for the attribute using the imported database enumeration are correctly created in any Editor Presentations using the enumeration as well as any "types and attributes" definitions using them.
However, no enumeration definition is created. The attribute definitions still have the ID of the database enumeration, but this now seems to point to a enumeration definition that does not exist...
I think that the export/import function should warn of these and leave the system in a valid state.
As a work around, I was thinking of manually recreating the database enumeration with the missing ID. Does anyone see any reasons that this strategy would not work to fix the problem ?
I created a PA with a database enumeration. I then exported the process template and imported it into a new RTC server. I then created a project area on the new RTC server based on the imported template.
The problem is that the work items using the database enumeration are invalid.
The definitions for the attribute using the imported database enumeration are correctly created in any Editor Presentations using the enumeration as well as any "types and attributes" definitions using them.
However, no enumeration definition is created. The attribute definitions still have the ID of the database enumeration, but this now seems to point to a enumeration definition that does not exist...
I think that the export/import function should warn of these and leave the system in a valid state.
As a work around, I was thinking of manually recreating the database enumeration with the missing ID. Does anyone see any reasons that this strategy would not work to fix the problem ?
