In a previous topic, I posted a solution for cross referencing sections of a generated document using bookmarks with the id of a Capella element.
Unfortunately, M2Doc no longer parses tags within Word fields. I am wondering if such a feature could be added, while keeping M2Doc tags in plain text.
I appreciate very much the use of plain text for M2Doc code, but this issue is forcing me not to upgrade to version 4.0.0.
Just mentioning FYI that M2Doc does not rely on hidden field any more because Microsoft 365 do not support them anymore.
Hi Stephane,
maybe I missed your point. The field code I mentioned is a standard REF one, and it applies to Office 365 Word. With the transition of M2Doc to plain text, cross references in generated documents would not need nested field codes anymore. Another option would be to add new tags to M2Doc syntax in addition to m:link, capable of generating page or section references.
Sorry my point was just to explain why we made that change in M2Doc 4.0, not to answer your issue. I don’t have enough knowledge here to help you.
Yes, I remember the way you used fields with M2Doc statements. The new way of parsing M2Doc templates breaks this (see this issue). I don’t think we should parse fields for M2Doc instructions since that defeat the goal of M2Doc 4.0.0. But yes a syntax in the text passed to the link to insert the page or section would be nice.
Hi Yvan,
I tried the new implementation of M2Doc snapshot supporting Page References and Section References. I would like to thank you for the quick implementation. I was able to easily convert my old template to the new syntax.
Thanks for the positive comment, that is greatly appreciated, Forums are generally the place where you hear about people having issues, so we also value this type of feedback 
Stephane