1
Bugs and Issues / Document Publishing: Heading Numbering in Custom Script Fragments
« on: September 13, 2022, 10:23:30 pm »
Hi everyone,
I am publishing a model as a custom document, where I currently have a main template, that is using a template fragment to output each element. The fragment uses a custom script to gather some data for each element.
My issue is with the numbering of the section headings. It seems as soon as I enable the custom section in the template, the heading level is fixed to the one used in the fragment, when it should be incremented according to the actual position in the output document.
So for example an element XYZ is a child of package "ABC", and in the final document the package is output as "1.2. ABC", I would expect the element heading to be numbered as "1.2.1. XYZ" for example. But it is numbered "1.3. XYZ" for example, so it seems it is always put to the same level as the parent. When I remove the custom section from the fragment and put some standard field as a heading in the element section, the numbering is as expected.
Is this a bug or am I missing something here?
Best regards,
Martin
I am publishing a model as a custom document, where I currently have a main template, that is using a template fragment to output each element. The fragment uses a custom script to gather some data for each element.
My issue is with the numbering of the section headings. It seems as soon as I enable the custom section in the template, the heading level is fixed to the one used in the fragment, when it should be incremented according to the actual position in the output document.
So for example an element XYZ is a child of package "ABC", and in the final document the package is output as "1.2. ABC", I would expect the element heading to be numbered as "1.2.1. XYZ" for example. But it is numbered "1.3. XYZ" for example, so it seems it is always put to the same level as the parent. When I remove the custom section from the fragment and put some standard field as a heading in the element section, the numbering is as expected.
Is this a bug or am I missing something here?
Best regards,
Martin
I tried the cloud login credentials, but that doesn't help...
.