Bullet point levels not exported properly

Document Generation
1

Hi all,

I experience an issue in Capella 1.4.2 with M2Doch 3.2.0.
Some of my element descriptions have bullet point lists with more than one level.
For the element (a diagram), I use the query diagram.documentation.fromHTMLBodyString().
The content gets exported correctly, but all are set to level 1.
For example, the description

- Level 1
  - Level 2
    - Level 3

gets exported as

- Level 1
- Level 2
- Level 3

Did I do something wrong or is this a problem on M2Doc’s side?

Thanks,
Jamo

2

It could be a bug in the HTML to docx conversion. Do you have the HTML code you are trying to convert ?
If you want to have a look at some working examples, you can check the ol tests and ul tests. The doc.html is inserted in the generated document.

3

I created the description from the Capella GUI. I select the element and then go Properties -> Description -> Open in Editor.

So any HTML formatting done, is done by capella.

I also tried it again in a new model with a new element. Same result: All bullet points are set to level 1.

4

Can you open the “Documentation” tab in the properties view. It should contains the HTML code of your description. If you can past the part regarding the bullet list problem, I might be able to find what is wrong.

5

This is what I see in the Docuementation tab

<p>This is an example bullet points list.</p>

<ul>
	<li>Level 1
	<ul>
		<li>Level 2
		<ul>
			<li>Level 3</li>
		</ul>
		</li>
	</ul>
	</li>
	<li>Level 1</li>
</ul>

<p>End of document.</p>

This is what I see in the exported document.
image

And these are the commands I used for this example:

{m:for entity | self.containedOperationalAnalysis.ownedEntityPkg.ownedEntities->select(x | x.name = 'OA 1')}
{m:entity. representationByDescriptionName('Operational Entity Breakdown').documentation.fromHTMLBodyString()}
{m:endfor}

The HTML code seems to be correct (which is why Capella displays it correctly). So I assume something goes wrong in the .fromHTMLBodyString() function.

6

I tested with your input and I reproduce the problem. I opened the following issue: