Enable grandfather revision for EPMDocument when imported to Windchill

[PD_12915986]

We have a requirement of enabling grandfather revision for EPMDocument when imported to Windchill from source to target Windchill system.

For example:

If the revision for the EPMDocument is A in the source system it should have new revision as AA, AB, AC..., AZ on the target system after importing and revising.

Similarly, if it is B it should have new revision as BA, BB, BC..., BZ on the target system after importing and revising.

Is there any way to achieve this custom revision?

[avillanueva]

Looks like all you are doing is advancing forward a great distance in the sequence. Once you import something at AA, normal revising would move to AB and AC as expected. So the issue is getting it in at the right starting point, a mapping. Curious as to what happens to new data after this migration? Normal new object creation would start at the beginning, A, and move up from there.

What is your migration path? How are you bringing this imported data from the source system? That is were you need to make the correction to change the revision on import. This article talks about loading at higher revision: https://www.ptc.com/en/support/article/CS166036?source=search

Loading EPMDocuments via LoadFromFile is not supported.

[PD_12915986]

We are trying to export the EPMDocument objects from the source Windchill system and importing to the target Windchill system using Import/Export Management functionality.
If the revision is A on the source system, on the target system it should be revision AA

We are marking revision A as legacy revision.

Similarly for B to Z.

[avillanueva]

What version to what version? You certainly want to look at the Windchill Bulk Migrator.