Skip to main content
G
Garvels1-Visitor
1-Visitor
April 9, 2018
Question

Graphic Entity can not be resolved when using Save Application

  • April 9, 2018
  • 1 reply
  • 2678 views

I am attempting to publish an xml document and all its dependencies, and am using the Tools -> Save Application function. However, I am getting an issue where all of the referenced graphics are saved under /portable_doc/portable_doc_files/ with completely different names. Then, in the log file it states that the "Graphic entity can not be resolved." Is there any way to prevent these references from being lost or these files from being renamed?

1 reply

R
RayStachowiak1-Visitor
1-Visitor
April 9, 2018

I am confused, Why are you using the save application function again. If you want to publish you can open the document in the editor and publish from the editor using  Publish command to PDF or whatever selection you need. the save Application is use dot save a document and its pulsing environment for troubleshooting. at least that is what the documentation states. I have never used it myself. Let me know more about what you are doing and maybe I or someone else on this community can help you.

G
Garvels1-VisitorAuthor
1-Visitor
April 9, 2018

I need to be able to save the document as xml, while also saving all of its file entities as xml as well, as well as maintaining image references. If you know of another way to do this, I'd be eager to hear it. So far, Save Application has been the only way to save each of the file entities as well in one command. 

Also, I'd like to specify that I am saving locally a document that is in Windchill.

B
18-Opal
bfriesen18-Opal
18-Opal
April 9, 2018

Are you using TIA or SMA application? We noticed that when we switched from SMA to TIA that the appsave changes the names of the image files. The only way around it for us was that our Simonsoft CMS displays a list of images used in the document. We could use that list with a custom program to extract the original image numbers from their save location.

 

Bryon

Terms & ConditionsCookie settingsAccessibility statement