# Infor LN Report Designer and Report Personalization Checklist > Source: https://netray.co/tools/infor-ln-report-designer-personalization-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Checklist for changing Infor LN report output on-prem: choose between Report Designer personalization and a new report, build, route output, test and deploy. ## Category infor-ln ## Erp Infor LN ## Audience - LN developer - LN technical consultant - LN key user ## Tool **Kind:** checklist **Groups:** #### Choose the route **Items:** **Text:** Write down what must change: layout and styling only, extra fields, or new logic **Critical:** true Layout, styling and field changes on a standard report: use a Report Designer personalization and leave the standard report untouched New calculations or data from other tables: a new or copied report in Reports (ttadv3530m000) in a customer VRC Reports already designed for an external reporting tool such as SSRS: change the report design (for SSRS, the RDL file) in that tool, not the 4GL layout Check whether the requirement is better met by a standard report option or a different standard report first **Text:** Confirm the Report Designer and personalization features available in your exact LN release before you plan the work **Critical:** true #### Build **Items:** **Text:** Never edit a standard report in the standard VRC; copy or personalize instead **Critical:** true Name new reports and personalizations by a convention that shows owner, purpose and change number Keep report script logic minimal and documented; heavy logic belongs in the session or a library **Text:** Check which personalization levels exist for the report and which one applies to each user at print time **Critical:** true Record the change in the customization register #### Device and output **Items:** Check the device definition the users print to in Devices (ttaad3100m000) and its device type Test PDF and printer output separately; fonts and page sizes differ by device type If documents are distributed electronically, confirm Document Output Management is available and configured in your release Set up and test email delivery for DOM document types, including the recipient per business partner Confirm archive or document management storage of printed documents, if used #### Test **Items:** **Text:** Print in every language the report is used in; translated labels change field widths **Critical:** true Print in each company that uses the report, including shared-table companies Test page breaks, group headers and totals with multi-page data Test with large data volumes to catch slow selections Test with a normal user role, not only an administrator Compare totals with the standard report for the same selection #### Deploy **Items:** **Text:** Move personalizations between environments with the export and import method your release supports, and keep the export file as evidence **Critical:** true Assign the personalization to the intended users, roles or company and no wider Transport new reports through the normal change process Keep a rollback: delete or deactivate the personalization, or reinstate the previous report version Tell users which report and device to use, and when the change takes effect **Scoring Note:** The critical items protect upgrades: a standard report left untouched keeps receiving Infor fixes. Do not deploy until every critical item is checked. ## Content **Intro:** 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. **Sections:** #### Choose the route first **Body:** 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 **Body:** 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. **Bullets:** - Reports: ttadv3530m000 - Program Scripts / Libraries: ttadv2530m000 - Devices: ttaad3100m000 - Logs: $BSE/log #### Worked example: adding a field to a sales order acknowledgement **Body:** 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 **Body:** 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. **Cta:** 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. **Faq:** #### What is the Infor LN Report Designer? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms infor ln report designer, infor ln report personalization, document output management in infor ln, infor ln sales reports, infor ln report designer development guide, infor ln reporting, infor ln reports, infor ln report --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json