Infor LN & BaanFree checklistPDF, Excel, Word exportInfor LNAll Infor LN and Baan tools

Infor LN Report Designer and Report Personalization Checklist

This checklist helps LN developers and key users change report output on an on-prem Infor LN system without breaking upgrades. It covers choosing between Report Designer personalization and a new report, building, routing output, testing and deploying.

0%

0 of 27 items complete

6 critical items still open - these are the highest-risk gaps.

Download checklist:

Choose the route

Build

Device and output

Test

Deploy

The critical items protect upgrades: a standard report left untouched keeps receiving Infor fixes. Do not deploy until every critical item is checked.

Get your report change routed the right way

Describe the report change you need and your LN release and we will tell you whether a personalization or a new report fits, and what to test.

Optional. The tool and every export work without this. No spam.

Was this tool useful?

Choose the route first

The most expensive report changes are the ones done the wrong way. The Report Designer lets you adjust layout and styling of a standard report as a personalization, so the standard report stays as Infor shipped it and keeps receiving fixes. Personalizations are stored separately from the report definition, which is why they survive solution installs on the standard report. When you need data the report does not select, or new logic, a copied or new report in Reports (ttadv3530m000) in a customer VRC is the right place. Reports that are rendered by an external reporting tool such as SSRS are changed in that tool rather than in the 4GL layout.

Where this lives in LN

Report definitions, including their layouts and report scripts, are maintained in Reports (ttadv3530m000) inside a package VRC, and customized reports belong in a customer VRC. Report Designer personalizations sit on top of a standard report; check the Report Designer Development Guide for your release for which levels a personalization can be assigned to and which one LN uses when several apply. Output goes to a device defined in Devices (ttaad3100m000), whose device types cover printers, Windows printers, external reporting and Document Output Management.

  • Reports: ttadv3530m000
  • Program Scripts / Libraries: ttadv2530m000
  • Devices: ttaad3100m000
  • Logs: $BSE/log

Worked example: adding a field to a sales order acknowledgement

Sales wants the customer item code and a payment terms note on the order acknowledgement. The field is already selected by the report, so a Report Designer personalization is enough: the developer adds the field, adjusts spacing and saves. Testing covers English and German output, a 3-page order and both companies that print acknowledgements. The personalization is exported from the test system, imported in production and assigned to the users who print acknowledgements. If sales later wanted a calculated delivery promise, that would need a copied report with script logic instead.

Gotchas

Personalization precedence catches people: a personalization made for one user during testing can override the one intended for everyone, so that user sees a different layout. Clean up test personalizations before go-live. Translated labels can push fields onto a second line, so test every language. Email output through Document Output Management depends on the release and its configuration; confirm which DOM features your release supports in its user guide before promising them. Finally, a copied report in a customer VRC no longer receives Infor fixes to the standard report, so record it and compare it after each solution install.

Frequently Asked Questions

What is the Infor LN Report Designer?

It is the LN tool for adjusting the layout and styling of standard reports without changing the standard report or using an external reporting tool. Changes are saved as report personalizations, separate from the report definition, so the standard report keeps receiving Infor fixes. Details are in the Infor LN Report Designer Development Guide for your release.

How do I move a report personalization to production?

Export the personalization in the test environment and import it in production using the method your release documents, then assign it to the intended users or group. Treat it like any other change: approved, tested and recorded, with the export file kept as the transport evidence.

What is document output management in Infor LN?

Document Output Management (DOM) distributes documents and reports electronically based on document type, channel and recipient, for example invoices by email to one business partner and on paper to another. It appears as a device type in LN device data. Check the DOM user guide for your release for the exact setup, including email.

Can I change LN sales reports without a developer?

For layout, styling and fields the report already selects, a trained key user can often use the Report Designer to create a personalization. Anything needing new data, logic or a different selection needs a developer and a report in a customer VRC. Either way, follow your change process before production.

If you want users to ask your LN data in plain English instead of waiting for a new report, we can set that up on your own servers.

ArchRay builder
Design the on-prem AI stack for Infor LN and Baan: model, GPUs, RAG pipeline, guardrails
See memory, speed and cost as you swap parts, then export the diagram. Free, in your browser.
Open the builder

Keep exploring

Free tools

ERP fixes and how-tos

Guides

Integrations

Comparisons