You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the exhibit upload tool to add multiple exhibits, the Table of Contents (TOC) displays wrong page numbers. Following the first exhibit, each subsequent exhibit page number shown in the TOC will be off by a higher number.
Example: A user uses the tool to upload three separate 1-page documents. In the final exhibit document, the TOC will say that Exhibit A starts on page 3, which is correct. However, it will then say that Exhibit B starts on page 6 (actual start is page 5) and Exhibit C on page 9 (actual start is page 7).
This issue is mostly likely being caused by the logic in the default docx template for the TOC, shown below:
Replacing exhibit.start page + loop.index + table page length - 1 with exhibit.start page + 1 (shown below) seems to have resolved the issue for me when cover pages are included. However, this will need to be tested further.
The text was updated successfully, but these errors were encountered:
When using the exhibit upload tool to add multiple exhibits, the Table of Contents (TOC) displays wrong page numbers. Following the first exhibit, each subsequent exhibit page number shown in the TOC will be off by a higher number.
Example: A user uses the tool to upload three separate 1-page documents. In the final exhibit document, the TOC will say that Exhibit A starts on page 3, which is correct. However, it will then say that Exhibit B starts on page 6 (actual start is page 5) and Exhibit C on page 9 (actual start is page 7).
This issue is mostly likely being caused by the logic in the default docx template for the TOC, shown below:
Replacing
exhibit.start page + loop.index + table page length - 1
withexhibit.start page + 1
(shown below) seems to have resolved the issue for me when cover pages are included. However, this will need to be tested further.The text was updated successfully, but these errors were encountered: