tavol index

[3DieCol]

Good morning to all,
I need your advice: are in the phase of "planning" of a very complex project, consisting of hundreds of tables. as first table I created a "complete" of machine (profile draft) with attached a separate of the parts that make up the above total; In the separate parts I used the property text %{number object|g}, so that there is a general index of the parts.
Now, what would I do? I'm trying to create a cartouche, for all subsequent boards, with a field called "index", that is custom property within it that goes to read that number obtained from the general distinction in the first table. I would practically like to go to create a reference, like a page number, so that once you create the album of the parts there is always order.
If anyone had any idea, I'd be grateful. Sure, I could add a custom property for each draft file, but I would like to find an automated route, even because if you had to add other parts inside, I would like the index to update automatically.
Thank you very much in advance, good work to all.
disability

 

[Be_on_edge]

Good morning to all,
I need your advice: are in the phase of "planning" of a very complex project, consisting of hundreds of tables. as first table I created a "complete" of machine (profile draft) with attached a separate of the parts that make up the above total; In the separate parts I used the property text %{number object|g}, so that there is a general index of the parts.
Now, what would I do? I'm trying to create a cartouche, for all subsequent boards, with a field called "index", that is custom property within it that goes to read that number obtained from the general distinction in the first table. I would practically like to go to create a reference, like a page number, so that once you create the album of the parts there is always order.
If anyone had any idea, I'd be grateful. Sure, I could add a custom property for each draft file, but I would like to find an automated route, even because if you had to add other parts inside, I would like the index to update automatically.
Thank you very much in advance, good work to all.
disability

that of the single draft is a recurring theme that I personally disagree with; in a few words to get what you want there is a lot of manual work to do (with risk of errors) for a modest benefit. You should automate several things to make everything error-proof, the thing is also feasible but in the end you would have a unique draft of hundreds of pages, which would have a significant impact on performance.

the best thing is that each component has its draft on which code and revision of the part appears. you will then have a draft of the complete list of parts which will bring back code (and possibly revision) description and quantity of components.
created pdfs of all boards you can then join them together and create an index with one of the various free pdf creators or not.

 

[3DieCol]

that of the single draft is a recurring theme that I personally disagree with; in a few words to get what you want there is a lot of manual work to do (with risk of errors) for a modest benefit. You should automate several things to make everything error-proof, the thing is also feasible but in the end you would have a unique draft of hundreds of pages, which would have a significant impact on performance.

I have not been too clear: At the moment I have hundreds of drafts, each relating to a very specific part, which, as you rightly say, has code, description, revisions etc.
what I want to do is to have, in the cartiglio of each draft, an "index" field, that goes to connect with the distinct parts of the draft file of the "complete" design, with the list of all parts; I need a field that goes to dialogue with the index number reported in a specific draft.
what I do not love, and that I would avoid, is to create something unique in pdf; for my experience to have a copy (pdf) of the work that does not constantly dialogue with the counterpart of the solid edge ecosystem, goes to create potential errors (i.e. copies of drawings that are not updated etc.). I don't love pdfs, all here, I usually use them (and gate them) as soon as possible.

 

[Be_on_edge]

I have not been too clear: At the moment I have hundreds of drafts, each relating to a very specific part, which, as you rightly say, has code, description, revisions etc.
what I want to do is to have, in the cartiglio of each draft, an "index" field, that goes to connect with the distinct parts of the draft file of the "complete" design, with the list of all parts; I need a field that goes to dialogue with the index number reported in a specific draft.
what I do not love, and that I would avoid, is to create something unique in pdf; for my experience to have a copy (pdf) of the work that does not constantly dialogue with the counterpart of the solid edge ecosystem, goes to create potential errors (i.e. copies of drawings that are not updated etc.). I don't love pdfs, all here, I usually use them (and gate them) as soon as possible.

Okay, now it's clear; the unique index field you already have it and is the sum of code + revision that you can make appear in the table.

on the pdf speech and the design always updated are not very agreeable; the pdf is the factual state at the time of its creation (release) that goes to armor the revision; the draft reflects the progress of a design \ revision, but until there is a release can not represent the production, you would lose control.

If you work in "continuous plumft" you can never trace to what you are producing.

 

[3DieCol]

Okay, now it's clear; the unique index field you already have it and is the sum of code + revision that you can make appear in the table.

I have to look into this point because I have not understood it, in the company we use a special coding (which at the moment I check and hand-in to every part/aid), if you have a way to explain to me in detail I would be grateful

on the pdf speech and the design always updated are not very agreeable; the pdf is the factual state at the time of its creation (release) that goes to armor the revision; the draft reflects the progress of a design \ revision, but until there is a release can not represent the production, you would lose control.

If you work in "continuous plumft" you can never trace to what you are producing.

in my reality, where every day "traffic" with a huge number of boards (they are only as a figure of designer, it is a really intricate work), I find better to work with the drafts, than release and revision where it serves; often there are daily revisions, and therefore I am afraid that with the pdf there are in the server obsolete versions of the draft counterparts, all here. I am not against pdf, only that I am afraid to lose control, all here :d
Thanks for the help for now.