Skip to main content
16-Pearl
August 7, 2014
Question

Changes saved to Workspace lost. Help please

  • August 7, 2014
  • 2 replies
  • 2977 views

Greetings,

We have a user who says that changes to SolidWorks CAD files saved to his Windchill PDMLink 10.1 workspace did not get saved.

He spent a few hours updating a drawing yesterday, saved to his workspace and now this morning he says the work was not saved?

On the Windchill side the object has been revised and is checked out at E.0. So in Windchill, there are no updated files.

In his workspace I see the same E.0.

Is there a different location to see the change history?

Any ideas?

2 replies

1-Visitor
August 11, 2014

Hi Landric,

I'll move this thread to the Windchill Community as you will likely have more success asking there.

lgrant16-PearlAuthor
16-Pearl
August 11, 2014

Here is a bit more info on the two situations are users have had.

We are using Windchill PDMLink 10.1 M040

These are both SolidWorks 2013 CAD files via the PTC Workgroup manager.

User 1: Check out objects to Workspace and make changes. Changes Saved to workspace. Then user Checked In to Windchill from the Workspace and chose the Remove from Workspace option. After the screen completed the workspace was displayed with the same files shown. There was no errors reported at the bottom of the screen.

User then selected the objects and selected to Remove from Workspace, user was presented with a warning message that changes would be lost. Ignored the warning. Checked Windchill and the objects had been checked in with the changes saved.

User 2: Check out objects to Workspace and made changes. Then users saved to Workspace. Two days later the user opened up the workspace and the objects but the changes had not been saved. Changes had been saved to the workspace but not Check Into Windchill so all work was lost.

12-Amethyst
August 14, 2014

Sounds familiar to me (we are working with Windchill 10.1 M040 and Creo Elements/PRO). Users forget to check if the action took place, and both environments (WC and ProE) are rather poor in warning the user when an action didn't took place.

For user 1, the checkin didn't took place (for whatever reason). For user 2, the save didn't took place (for whatever reason). Reasons can be divers: access rights, regeneration status, family table conflicts, etc.