Hello Ken De Wachter ,
I hope I can:
As far as I know, in what is called "Editor view navigation pane", only text nodes of XML documents can be made visible.
On the other hand in the popup that can be opened from the "Document Structure column", you can visualize virtually everything:
text nodes, attribute values, XML comments and even content of processing instructions.
I hope this is the answer you were looking for.

Regards

Frank

Hi Frank,

Thanks for your response. I managed to configure the Document Structure column without many issues. It's a relatively easy and powerful feature. However, having to click it every segment to see the product ID is a bit of a drag...

In the post I refer to, it seems like you found a solution 3 years ago:

thanks for your reply. I was on the wrong track. The way to obtain the values I want, is to define parser rules for "Name" elements (translatable and non-translatable ones) and then it is possible to have the names displayed in the Document Explorer. And if I want to see both the hierarchy of products and the names, I need to enable "ShowElementContent" for both elements.

Any clue what you meant by that? (c:

Ken De Wachter said:

Thanks for your response. I managed to configure the Document Structure column without many issues. It's a relatively easy and powerful feature. However, having to click it every segment to see the product ID is a bit of a drag...

Ken De Wachter

Why not install this plugin?

https://appstore.sdl.com/language/app/dsi-viewer/995/

Takes the drag out of it ;-)

What I meant three years ago is the following:
If you want to display text node content in the "navigation pane", you need to define a parser rule for the specific element, even if this parser rule is not needed for anything else, since this element is supposed to be handled in the Studio default manner (structure and not inline / translatable unless "not-translatable" is inherited from higher hierarchical level).
(You will probably know that defining XML parser rules (for a specific element) is only needed, if the node should be handled in a non-default way.)
In the "Document Structure Information" column on the other hand, you are able to extract XML content from a completely different part of the XML document using relative XPath statements that allow you to extract virtually whatever XML node you are interested in.

What I meant three years ago is the following:
If you want to display text node content in the "navigation pane", you need to define a parser rule for the specific element, even if this parser rule is not needed for anything else, since this element is supposed to be handled in the Studio default manner (structure and not inline / translatable unless "not-translatable" is inherited from higher hierarchical level).
(You will probably know that defining XML parser rules (for a specific element) is only needed, if the node should be handled in a non-default way.)
In the "Document Structure Information" column on the other hand, you are able to extract XML content from a completely different part of the XML document using relative XPath statements that allow you to extract virtually whatever XML node you are interested in.