cartiglio and recall property

[Crios816]

Good morning.
Starting from an autocad cartoon I made the template to use with solid edge.
the various fields of the cartiglio:
- code.
- material
- type of treatment
- description
- revision
- etc.
they auto-compil because I tied them to the fields that are in the "file property" of the part.

the problem arises when I insert multiple sheets, because in the template I inserted the recalls of the properties with this syntax:

%{titolo|r1}

when I put the second sheet in the field of cartilage always appears the title of the part present on sheet 1.
so when I insert 3, 4, 5 sheets the field where there is the call %{titolo|r1} always reads the part present on sheet 1.

Can anyone help me?
Do you know if there's a call that reads the ownership of the part regardless of the sheet number?
Thank you.

 

[cacciatorino]

Can anyone help me?
Do you know if there's a call that reads the ownership of the part regardless of the sheet number?
Thank you.

%{titolo|r2}
%{titolo|r3}
.
.
.
.
%{titolo|rn}

But it's a practice that has its own risks. If you've talked about it in the past, try to do an archive search.

Bye.

 

[Crios816]

Bye.
I looked at previous posts, but I didn't find what I wanted.

as you wrote, this is a method, but it involves that for each sheet I have to manually enter the code.
what I want to do is that every time I add a sheet automatically take the properties of the object I put in the second sheet.

are there solutions?
Thank you.

 

[delki]

only those already predicted, that is by hand. Otherwise you need to make a macro. the best solution however is to make a table (and therefore a dft file) for each built 3d element and for which it serves the table.

 

[abro]

only those already predicted, that is by hand. Otherwise you need to make a macro. the best solution however is to make a table (and therefore a dft file) for each built 3d element and for which it serves the table.

Does anyone know if this paleolithic system was exceeded in the ver.2023?
Thank you.

 

[Be_on_edge]

Does anyone know if this paleolithic system was exceeded in the ver.2023?
Thank you.

the practice of putting in the same file several parts is not widespread and consequently no steps have been made in this direction. to continue working in this way you need to create the appropriate files according to the page number.

a draft for each part remains the most flexible solution, even to be able to reuse the parts for other projects

 

[abro]

I understand that it may be uncommon, but personally having all the boards in one file I find it comfortable and neat.
cmq create the possibility to link not only the name of the part, but also the name of the view inserted I do not see an unsurpassed rock considering that for sw it is practice

 

[Be_on_edge]

I understand that it may be uncommon, but personally having all the boards in one file I find it comfortable and neat.
cmq create the possibility to link not only the name of the part, but also the name of the view inserted I do not see an unsurpassed rock considering that for sw it is practice

It is not an unsurpassed rock but simply there are no demands to carry out development in this direction.

if it is important for you the first step is to make a request for improvement through your dealer by explaining the benefits that would take your job. more demands of the same type there are more possibilities than it is realized there are.

then always remains the possibility to create a macro\program that does exactly what you ask