original replacement --> previous recurring version

[ferro.84]

Good morning to all,
we have a combination a that contains a part/group b (part or group is indifferent).
I'm trying to figure out how to save a previous version of b (laughs) b _ prec) so that the next upload a,
it has inside b _ prec, anziché b.
tell me if I do right:
1) Loading the aid a;
2) load, with the baffled option "load as vers. part/grp" part/group b _ prec;
3) I use the command "replace with version", indicating as original b (which in the structure list is inside a) and as a b_prec version (which is rooted in the structure list and has the yellow/brown icon).

I saw that replacement is done properly for b, but if he has inside the sub-parts/groups c, shared with other groups a, it is not said that they are also replaced.
result: I still stay with yellow/brown icons here and there in the structure list!

you can not tell the cad replace everything with the previous version, thus acting in a recursive way on how much I have to video?

Thanks for the help

 

[cacciatorino]

do new session, then charge b_prec and then a. all that is already present at video when you load "a" should be prevalent compared to what analog already saved in "a" itself.

 

[reb_bl]

The less groups you will do, in this case especially, the better you will go to make this kind of replacements.
Dispassionate advice: a few groups and all logical ones or all the pieces that move together, avoid as much as possible to make a group for an electric motor, always join it in one part, it will be easier to handle and if you do not have pdm an entity (group) less to manage.

 

[ferro.84]

The less groups you will do, in this case especially, the better you will go to make this kind of replacements.
Dispassionate advice: a few groups and all logical ones or all the pieces that move together, avoid as much as possible to make a group for an electric motor, always join it in one part, it will be easier to handle and if you do not have pdm an entity (group) less to manage.

I'm trying to convince my colleagues.
right today I found a group with inside a motor made from a step: thousand thousand thousand parts and nested subgroups!

 

[ferro.84]

do new session, then charge b_prec and then a. all that is already present at video when you load "a" should be prevalent compared to what analog already saved in "a" itself.

I know this already, but I want to avoid doing this, I explain why.
in the company we are without pdm.
each user works on their own group and one of them works on the layout that contains them.
to update the layout, as you say, I should do a new session, upload all the groups on which users worked, upload the layout and save it.
this implies that to update the layout I must always download it and reload it and if the file is heavy you lose a lot of time.
with version replacement, instead, the layout loads it once, and with him to video I load in version the individual groups and replace them.
In theory, I thought everything was replaced, but that's not exactly what it is. .

 

[reb_bl]

I know this already, but I want to avoid doing this, I explain why.
in the company we are without pdm.
each user works on their own group and one of them works on the layout that contains them.
to update the layout, as you say, I should do a new session, upload all the groups on which users worked, upload the layout and save it.
this implies that to update the layout I must always download it and reload it and if the file is heavy you lose a lot of time.
with version replacement, instead, the layout loads it once, and with him to video I load in version the individual groups and replace them.
In theory, I thought everything was replaced, but that's not exactly what it is. .

try to see on the German site, it seems to me there was a lisp that updated everything, in any case it is a delicate mooolto procedure, go with the feet of lead.

 

[reb_bl]

I'm trying to convince my colleagues.
right today I found a group with inside a motor made from a step: thousand thousand thousand parts and nested subgroups!

I resigned with my colleagues, I told them how to proceed correctly, but they always did as they wanted, telling me that "it was enough to copy everything to 1 level". ...

 

[cacciatorino]

I know this already, but I want to avoid doing this, I explain why.
in the company we are without pdm.
each user works on their own group and one of them works on the layout that contains them.
to update the layout, as you say, I should do a new session, upload all the groups on which users worked, upload the layout and save it.
this implies that to update the layout I must always download it and reload it and if the file is heavy you lose a lot of time.
with version replacement, instead, the layout loads it once, and with him to video I load in version the individual groups and replace them.
In theory, I thought everything was replaced, but that's not exactly what it is. .

using modeling in team without having a pdm would lose patience to a saint.... buying it is definitely a good investment.

 

[reb_bl]

in the company we are without pdm.

take away my curiosity, will it be because the pdm "wine too much, is it too rigid..."?

 

[ferro.84]

take away my curiosity, will it be because the pdm "wine too much, is it too rigid..."?

We are still too few, so they say, and it is not worth it..vabbé. .
thank you all for the support, luckily it is Friday!
Good weekend

 

[cacciatorino]

according to me from two up it is already necessary!

 

[reb_bl]

according to me from two up it is already necessary!

uff! how not to quote!! ! !

when you open a nice pkg full of empty groups, at that time there you start to hope!

 

[cacciatorino]

We are still too few, so they say, and it is not worth it..vabbé. .
thank you all for the support, luckily it is Friday!
Good weekend

I give you two numbers to get an idea: the license model manager currently costs 590 per year, and it needs one for each client. then serves a db editor license that costs about the same and needs one for every 7-8 designers (it's a floating license that can be taken and released manually).
if you use ms-sql database you should be protected from other license fees up to a number of clients (using sql express which is supported). if you use as an oracle database instead consider that the mm-oracle connector is paid.

the pdm as it is supplied can already be used to work on the net, and some small customizations can be done at home (users, anagraphic properties). for other more complex things, on the other hand, it is necessary to help a supplement and there prices can rise a lot.

 

[ferro.84]

I give you two numbers to get an idea: the license model manager currently costs 590 per year, and it needs one for each client. then serves a db editor license that costs about the same and needs one for every 7-8 designers (it's a floating license that can be taken and released manually).
if you use ms-sql database you should be protected from other license fees up to a number of clients (using sql express which is supported). if you use as an oracle database instead consider that the mm-oracle connector is paid.

the pdm as it is supplied can already be used to work on the net, and some small customizations can be done at home (users, anagraphic properties). for other more complex things, on the other hand, it is necessary to help a supplement and there prices can rise a lot.

thanks for this information! I will try to convince the leaders (and colleagues), although now it seems there are other priorities in the company. I will let you know! In the meantime I will continue to ask for wisdom with other requests with new discussions

 

[cacciatorino]

thanks for this information! I will try to convince the leaders (and colleagues), although now it seems there are other priorities in the company. I will let you know! In the meantime I will continue to ask for wisdom with other requests with new discussions

other important info: model manager works so as to interpose between the cad and the database, in the sense that the files are saved in a way not understandable to the human

If in a future you decided not to use the pdm you would find yourself with an inextricable cluster of rows without head or tail, and the only way out would be to save everything back in pkg (and me for the tables), before the expiry of the licenses of model manager