Skip to main content
Question

Regression in Indicium (from 2026.2.11 onwards): Label print orientation forced to Portrait

  • August 27, 2026
  • 5 replies
  • 32 views
Mark Poorthuis
Sidekick
Forum|alt.badge.img+1

Since our upgrade to 2026.2, we have encountered a critical issue with label printing. Labels are unexpectedly printed in Portrait instead of the configured Landscape orientation, causing the output to be cut off.

After verifying the report layout, Software Factory settings, and printer driver configurations, we isolated the root cause to Indicium:

  • 2026.2.10: Prints correctly in Landscape

  • 2026.2.11: Incorrectly prints in Portrait

  • 2026.2.12: Incorrectly prints in Portrait

As a temporary workaround, we have rolled back to Indicium 2026.2.10. Given that this is an essential continuous production process, could this regression please be investigated so we can safely adopt upcoming Indicium releases?

(See attached photo for the cut-off print result)

 

Enabling your low-code solutions

    5 replies

    Mark Poorthuis
    Sidekick
    Forum|alt.badge.img+1

    TCP ticket: 15800I

    Enabling your low-code solutions
    T
    Moderator
    • Tim Scholten
    • Moderator
    • August 27, 2026

    Hello Mark,

    We are aware of the issue and we will let you know when we have an update.

    Mark Poorthuis
    Sidekick
    Forum|alt.badge.img+1

    Thanks for the update—good to know it's being addressed.

    For future reference, where are known issues like this typically published? We spent the last four hours troubleshooting across the report, Software Factory, and printer drivers before isolating it to Indicium. Knowing where to check for active regressions or known bugs would save a lot of time before diving into a lengthy investigation.

    Enabling your low-code solutions
    Arie V
    Community Manager
    Forum|alt.badge.img+12
    • Arie V
    • Community Manager
    • August 27, 2026

    ​@Mark Poorthuis On your last question: at some point we did maintain this blog, but that isn’t being maintained at the moment. It proves hard to determine what kind of known issues should and should not be mentioned there. But it’s a fair question, so I’ll reconsider how we can get a Known issues list working for all of us.

     

    Mark Poorthuis
    Sidekick
    Forum|alt.badge.img+1

    Thanks for the transparency and for reconsidering this. Kees closed

    Enabling your low-code solutions
    Terms & ConditionsAccessibility statement