"Source Object cannot be null" when Checking In an EAM

[freym05]

Consistently receiving the message :

"Traceability Link 'Data 'Animal Demographic'' (Data 'Animal Demographic'): Source Object cannot be null."

For multiple (~10) Data Object that are configured as Traceability Links within a EAM System Object. These Data Objects have been imported from a CDM (i.e. Entities). I have conducted Impact and Lineage research and tried to review the documentation.

Specific questions:

(1) What does this mean?

(2) How to go about researching the problem and correcting it?

These Imported Objects are being used as a reuse mechanism to effect Impact and Lineage for Data across a large appliocation ecosystem within multiple EAM's.

Thanks in advance. -Mike

[freym05]

One last thing, 16.6 SP03 (we are moving to 16.6 SP05) seems to have some issues associated with Traceability Links generally speaking. I just opened a ticket where Replicated System Objects containing Data Object Traceability Links (as above) are removed after I save a reopen the container EAM. PD Support has recreated the issue and is working with Development. Cheers.

[freym05]

George, thanks for the quick follow-up, executing a Traceability Links "List of" Report shows the Linked Object (i.e. Data Object in this case), Source Object as "<None>". The Traceability Links were created via Tools>Import of Entities into an EAM and importing them as Data Objects having Traceability. I just need to swap these out with new imported Data Objects that have the Source Object populated. Strange, I cannot think of any odd behavior that would have "broken" the Traceability. Thank you once again.

[GeorgeMcGeachie]

This works in PD 16.6.6.0 (SP06) - if you haven't moved to SP05, move to SP06 instead

[GeorgeMcGeachie]

1) somehow, the source object on the Traceability links is missing

2) You can verify this by creating a List Report that contains Traceability Links.

How did you import the Traceability links?