#1
|
||||
|
||||
Share obj and MM
We have just passed in Model Manager from WorkManager
All good, but I there is a problem If i load a part of MM and then load the same part, saved locally before switching to MM instead of sharing it keeps me as a sort of "version" And it add some king of 3 green squares Having the same ID may simply not share it with WorkManager as it did before? "BLA BLA BLA was loaded. Previously and was automatic. Shared (instead of reloading)" It say this no more How can I fix this? THANKS.. |
#2
|
|||
|
|||
Re: Share obj and MM
Why are you "saving locally"? Model Manager does not like this situation. Don't know why CoCreate decided that their PDM system must ALWAYS be connected live to a network in order to ensure the integrity of the data...only PDM system I have ever encountered that does it this way...
|
#3
|
||||
|
||||
Re: Share obj and MM
1- I have a lot of model that i use that is locally
2- i have 2 PC, so to excange files between them i must save locally I need a setting like "if model have same ID, simply share it" I have seen if i enable data managment all work ok, it recognize it and share it. But i can't use MM and data managment at the same time... |
#4
|
||||
|
||||
Re: Share obj and MM
I do sometimes have reason to load from local computer but it seems it should not be part of normal business. It seems like you'll be better off if you can make the switch of getting your local files stored onto MM, so you have one source. Likewise once your models are saved into MM, it seems the easiest way to exchange files between the 2 PCs is use MM - save to MM from one PC, load from MM on the other PC.
To your question - I have tried loading a model from ModelManager, then saved it as a package and as a 3D Data. Then I reloaded the package and the 3D Data. In both cases, I got the messge "NOTE: '/DriveRoller.1' was previously loaded and has been automatically shared (instead of reloading it)." as expected. Do you have Load As Part/Assy Version checked in the Load dialog? What version are you working in? |
#5
|
||||
|
||||
Re: Share obj and MM
Quote:
Quote:
Quote:
Look at attachment AGGANCIO.001.pkg AGGANCIO.002.pkg Part have same ID, but different attribute If you load them, OSD don't share it :-( |
#6
|
||||
|
||||
Re: Share obj and MM
Someone tryed my attacment?
|
#7
|
||||
|
||||
Re: Share obj and MM
Up.........
|
#8
|
||||
|
||||
Re: Share obj and MM
Up.........
|
#9
|
|||
|
|||
Re: Share obj and MM
Hi,
One of your package has been saved onto your file system, and it has never been in saved into any Model Manager. We can say it's "MM clear". The second one has been saved onto the file system also, but after it has been saved into some Model Manager. It contains a property that testify it has been saved into a Model Manager database once upon the time. Then the 2 packages have slightly different properties internally. And this is what Modeling recognizes and differentiates when you load the 2 models. Modeling interprets one model as a version of the other (this is what the green symbol says). The model saved into Model Manager may have additional properties in the database (metadata) not known from the other one. They are not 2 instances of the same SysId model, but 2 versions of a common SysId model. If you connect again into Model Manager, MM will probably detect a SysId conflict. |
#10
|
||||
|
||||
Re: Share obj and MM
Ok, but there is not a way to automatically share it, becouse they have the same ID?
If i stard with "Data Managment" module it share it! But if i start with model manager it don't.. :/ |
#11
|
|||
|
|||
Re: Share obj and MM
Data Management and Model Manager have different policy on that topic.
But you can reintegrate in Modeling, as the following: When you uploaded your 2 models in Modeling, let use [Structure], [Version] and [Reintegrate]. You will select one of your model as "Reference" and the other one as "ToReintegrate". Then you will notice that your 2 models become shared since they have the same SysId. Depending on which part you choose as "Reference and as "ToReintegrate", you define which is the original. And when you will connect later to Model Manager you may have either a "Locally Modified" or "SysId conflict". |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|