Cartridge revision table configuration with automatic fills on up to 3 lines

[Anthony-R]

Hello

To start this cold week, I have a new request which this time concerns the revision table attached to the cartridge.

What I would like is to obtain 3 lines of revisions with the A index of creation remaining visible in addition to the last 2 indices.

The Visiativ dealer had told my colleagues (I was not yet part of the company) to use a revision table rather than including these hard lines in the basemap. It's true that it seems easier to manage (adding and deleting lines on demand) but it seems more difficult to set up automatically and the number of lines has to be managed manually.

Because what I would like is that, like in my old box, everything updates automatically (indices, dates, modifier name, approver) and that there are only a maximum of 3 hint lines. In this society, variables 0 (current revision), -1 (previous revision) and -2 (previous previous revision) were created. It worked except that, as the table included 3 rows, the index A was hidden from the index D because only D, C and B remained, whereas I would like D, C and A to remain.

My concern is that I don't know how to do it because I would like the same way of working but that India A still remains in place.

For the moment (attached image with the variables at the bottom and the associated names at the top), the A index has been created in the 1st^{line of} the bottom. The problem is that the last index would be on the top line and the previous index on the middle line, except that before being at the C index the A index would be visible on 2 lines, which is a problem.

Moreover, how do you change the variables from the current index (0) to the previous index -1?

Does anyone have the solution to these problems if it is possible?

After that, I'll have to set up all this and add the new variables to the EPDM workflow.

Thanks in advance ;-)

Antho

cartouche_avec_variables_et_noms.jpg

[flegendre]

This mode of operation speaks well to me, we had set up this solution exactly when the EPDM integration of the company where I worked before.

I don't hide the fact that without the EPDM consultant, we wouldn't have managed to set this up.

I don't remember everything, it's a bit old....

I don't have any documents from the time, I have to look at it.

When did you see this way of working?

[Anthony-R]

It was at Altor Industrie in Clisson (44).

It must have been the consultant Axemble who had set it up as well (before I arrived too!).

At worst, if I can't do it, we'll call on Visiativ too because it's still ideal to work automatically via the feeds because there's just the wording of the modification obviously to be written and that's it.

If you can get your hands on docs that would explain how to do it, I'd be very interested ;-)

[Cyril_f]

Hello

To be tested but with an entry formula I think it can meet the need.

For example, taking the names of your file properties as variables:

For Rev-1: %Revision(A=B)% (force Rev-1 to B when Revision is A)

For Rev: %Rev-1(B=)% (No-load Rev force when Rev-1 is at B)

[Anthony-R]

I would like to test but where can I enter these starter formulas?

[Cyril_f]

Good evening

In maps, selecting a field makes it the last input area.

[Anthony-R]

I modified the Revision variables by creating a variable "Revision modification" and another "Revision modification-1" to dissociate them from "Revision" which I also use as an annotated current index next to the plan number.

I entered these values as input formulas into the variables of the data map:

For "Revision modification": %Revision modification-1(B=)% (Revision modification force blank when Revision modification-1 is at B)

For "Revision modification-1": %Revision(A=B)% (force Revision modification-1 to B when Revision is A)

 

In index A: no problem, only the corresponding line is filled in

In index C: no problem, the 3 lines are filled.

In index B: it doesn't change anything, the values remain on the top line.

 

It seems very complicated to me, especially since it remains to be defined how the variables change level to go from modification to modification-1 in automatic...

I think we'll have to call on our consultant Visiativ, unless someone finds an explanatory precedence, flegendre ?

[olivier42]

(seen in another EPDM)

A technique to create rows manually from a revision table is to go through non-visible "buffer variables", which are just there to copy-paste a line, before re-writing it elsewhere...

[Anthony-R]

After snooping around in the tools, I may have a lead that seems to correspond to my needs: the RevisionTable application included in myPDMtools which allows me to automatically manage the filling of revision tables.

I'm going to try it!

presentation_revisiontable_-_mypdmtools.pdf

[Silver_Surfer]

A suggestion: now that PDM pro (and std) 2018 manages the revision tables, why not create in the title block the fields "Create by", "Date created" which corresponds to the index A, and let the revision table display the last 3, i.e. the D revisions, C and B.

In my opinion, it meets the need, and it's very simple to set up.

[Anthony-R]

Oh yes, indeed a great novelty, especially if it's simple!

Except that we are in SolidWorks 2017 and PDM 2017 as well. We would have to migrate...

[Silver_Surfer]

It is possible to keep SW2017 and migrate only PDM to 2018.

Attention to the server OS: SW 2018 server products require MS server 2012 or later.

I am currently in the same situation: the update to MS server 2016 to upgrade PDM to its 2018 version is scheduled for next week; so I can modify the config, take advantage of this new feature and test it while keeping SW2017 SP5.

FYI: except in exceptional cases like this one (to have time to modify and test a new feature), I only upgrade once a year to the SP5 of the new versions. A practice that has proven its worth.

[Anthony-R]

I managed to do what I wanted, with the help of our consultant Visiativ.

It seems to work by having hard-integrated the A index into the basemap and for the other indices a revision table managed by the PDM feed (excluding creation) and the myPDMtools RevisionTable tool which allows you to choose the number of rows and the variables to be integrated automatically.

Thank you @ all for your answers!

[guyom_d]

Hello Silver Surfer,

This subject also interests me in particular for the creation line (not wishing to hard-integrate the revision value, but a variable with the first revision value). Were you able to test with PDM 2018? What is the result?