Createing a Numbering list inside a text box


When we create a numbering list inside a text box and we want to preview the template, the first point of the numbering list is missing.
How can we prevent that from happening ?
Examples attached in the screenshots bellow.


Thank you,

Hi Stefan,

can you share your code for this text box?




Same thing happen with both

{% ifi != blank %}{% input as:text size:mini default:b6 placeholder:'Description'%}{% newline %}{% endifi %}


{% input item.description as:text placeholder:'Description' %}{% newline %}

Bellow is a part of the template.

{% comment %}<----Inter-company reporting procedure---->{% endcomment %}
{% stripnewlines %}
{% ic %}{% input custom.tick.section_F as:boolean %}{% endic %}
{% if custom.tick.section_F %}
{::font size="m"}**{% assign nbr = nbr | plus:1 %}{{ nbr }}) Inter-company reporting procedure**{:/font}{% newline %}
{% else %}
{% ic %}{::font size="m"} Inter-company reporting procedure{:/font}{% endic %}
{% endif %} 
{% if custom.tick.section_F %}
{% ifi != blank %}{% input as:text size:mini default:b6 placeholder:'Description'%}{% newline %}{% endifi %}
{% fori item in custom.section_F %}
**{% input item.header placeholder:'Header' %}**{% input item.attachment6 as:file_collection %}{% newline %}
{% input item.description as:text placeholder:'Description' %}{% newline %}
{% endfori %}
{% endif %}
{% endstripnewlines %}

Hi @Michiel

Did you had any time to check the code i have posted?

Thank you.

Hi Stefan,

I’m sorry for the late reply. The problem you encounter has all to do with mark down and unfortunately is not easy to fix. There is a workaround though: instead of 1. you can type

1\ .

and you will see in preview it’s the 1. you expected.

Another option is to use 1), 2), 3),…

Kind regards,



Thank you for letting me know.

Have a great week.


We’re facing a similar issue with numbering in free text box.
When writing:

  1. xxx
  2. xxx
  3. xxx

in a text box, all numbers starting from 2 until the end are misaligned with the 1st number in the pdf export. Everything looks fine in Silverfin preview.

This is part of the code :

{% capture improvements %}
[Exposé de la situation financière de la Société et description des mesures envisagées
Mesures possibles :]

1.	Une lettre de confort, déclarant que les ressources financières nécessaires ont été mises à disposition par ... et valables à compter de la date d'approbation des comptes annuels de l'exercice clôturé le ... pour une période de douze mois.
2.	Un apport en numéraire à la Société par le ou les actionnaires de la Société s'élevant au moins à ... EUR, à effectuer avant le ....
3.	Un apport en nature de créances à la Société par les créanciers de la Société s'élevant à au moins ... EUR, à effectuer avant le ....
4.	…
{% endcapture %}

{% if custom.special_report.conclusion_fr == "poursuivre les activités de la Société" %}
Enfin, {% if BV %}{% case director_type %}{% when 'board_of_directors' %}le conseil d'administration propose{% when 'manager' %}l'administrateur propose{% when 'managers' %}les administrateurs proposent{% else %}les administrateurs proposent{% endcase %}{% elsif NV %}le conseil d'administration propose{% else %}XXXXXXXXX{% endif %} de prendre les mesures suivantes afin d'améliorer la situation financière de la Société et de préserver la continuité de ses activités :
{% input period.custom.special_report.improvements as:text default:improvements required:true %}{% rollforward nil period.custom.special_report.improvements %}
{% endif %}

As mentioned above, writing 1\. temporarily fixes the issue but we cannot ask all our users to write like this. Is there anything that can be added to the code as a more permanent fix?

Thanks !


Hi @Gianluca,

We were able to simulate this too (thanks for your detailed case).

Afraid we’ll need to tackle this with our engineers team, so as soon as I have an update, we’ll get back to you.

Sorry for this inconvenience