We are troubleshooting an issue impacting community login, and it may be intermittently unavailable. Sorry for any inconvenience.
When running a publishAllLatestEPMDocNoDefault job in Windchill it picks up previous versions of an .ASM.
Now in this previous version it references a part that no longer exists, it has been renamed e.g. xxx-xxx.prt is now called xxx_xxx.prt
This means that the Worker can not publish the job because it can not retrieve xxx-xxx
What is best to do in this situation? I understand if this was a current version I should check the .ASM out, delete the part/locate the part and check back in.
I can't figure out how to update a previous version because you can't check it out and back in because it isn't the newest iteration?
I can't prohibit Publishing because when I do so it prohibits publishing on all versions of this item?
I understand this shouldn't of happened in the first place but there was no one monitoring at the time, there is now but we are trying to clean up the mess that has been created up until this point.
Any help would be much appreciated
Solved! Go to Solution.
OK I've answered my own question and for anyone reading this with similar issues: I was running a publishAllEPMDocNoDefault where I should have been running a publishAllLatestEPMDocNoDefault job
My question is then rephrased... is it possible to amend old iterations so they are up to date or is this just something that needs to be monitored and corrected at the time of an issue occurring?
Thanks
OK I've answered my own question and for anyone reading this with similar issues: I was running a publishAllEPMDocNoDefault where I should have been running a publishAllLatestEPMDocNoDefault job
My question is then rephrased... is it possible to amend old iterations so they are up to date or is this just something that needs to be monitored and corrected at the time of an issue occurring?
Thanks