Import/Export Management

[Turko]

Version: Windchill 13.0

Use Case: I am performing a an import of data from a source environment. Using the import/export management tool, I am presented with the following error when trying to do the import. "WTDocument: 123 ( 000073 ) A.2" cannot be imported because the revision "A" is invalid" The issue can be overcome when I check the "Resolve overridable conflicts" check box. I have checked the version sequence on both the source and target environment and they are identical.

Description:

Can anybody explain why I am receiving this error message?

[Marco_Tosin]

Take a look at these two articles

Import from 10.2 to 11 issue

Importing object fails with an error "cannot be imported because the revision "I" is invalid" in Windchill PDMLink

[Turko]

Hi. Thanks for getting in touch. I don't believe the info in the first URL explains why this error occurs - have I missed something? The second URL does but does not make sense to me as I have compared the version schemes in both of my environments and they are identical.

[Marco_Tosin]

Have you read the solution?

https://community.ptc.com/t5/Windchill/Import-from-10-2-to-11-issue/m-p/498208#M53899

[Turko]

Hi @Marco_Tosin - I have. I can't see how the solution explains why I am getting the issue I'm getting? Also, I'm not trying to perform an upgrade.

[Marco_Tosin]

I have pointed out some articles that explain some of the reasons that could have caused the error that the system is reporting.

You replied that none of these apply to your case and that you did everything correctly, but you still get an error.

Honestly, I don't know what else to say to help you.

[avillanueva]

Can you provide a sanitized copy or screenshot of your input file? Perhaps there is an error there.

[Turko · Accepted solution]

Hi. I think I've managed to resolve this. Despite the error message I was getting, I don't think the cause was anything to do with what the message was indicating. It seems that my workflow and lifecycle that the object type that import was trying to create included state names that had not been added to the correct modeled enumeration list. Once this was resolved and the workflow and lifecycle were usable, the import created the objects no problem.