NOTICE: Our Community is moving. Get more information.
UDAs Not Imported From Server A to Server B
I"ve exported a project from server A using RM-Export to be
imported into Server B. After using RM-Import to import the project
into Server B, some customized UDAs are missing. Why is this
Requirement Types are unique across a database. During Import,
if a Requirement Type is found to be already present in the target
database, the Target system will act as master and retain ALL
properties of the Requirement Type.
This is to avoid conflicts in the target database as adding
newer custom attributes to an existing Requirement Type would
affect all existing projects too.
The workaround to update the current custom tabs with the new
customized UDAs, so that the target system now has a placeholder or
bucket for the data that is being imported.
In the case that was presented, the Requirement Type has the
same name and the custom fields were not retained, but since the
Requirement Type has the same name, we would presume that the
customer expects the data to “merge” but it
doesn’t as the Target acts as the master. To get the
expected / desired result the best solution is to add custom tabs
prior to import to the Requirement Type. This results in 1
Requirement Type with all desired properties, instead of two
Requirement Types which confuses users and customers. Also
Requirement Types heavily impact performance, and these should not
be added in such a manner. Imagine where a customer does an
import several times and their test system has changed a few
iterations, or they have 4 smaller servers they combine into
one. It would be a nightmare to decipher which of four
“…functional requirements…” is the correct
one to use, or had the properties they desired”.
Author : Elaine Lim & Scott Moore