Infor LN Date Format: User, Language, Reports and Integrations
infor ln date format
Also searched as
- change date format infor ln
- infor ln date format dd/mm/yyyy
- infor ln date format reports
- infor ln date conversion bod
Short answer
In Infor LN the displayed date format is governed by the user's language and locale settings rather than one global switch. Change it in the user data and the language or regional settings, check the Web UI browser locale, and keep integrations on a fixed format such as ISO 8601 so display settings never affect the data.
Applies to: Infor LN 10.x, Web UI and classic client. Exact session names vary by release; use the session search to confirm.
How to change a date format
- 1Identify the layer that is wrong: the user's LN settings, the language definition, the Web UI browser locale, or a report layout.
- 2Open the user data for the affected user in Tools and check the language and any date or regional settings assigned to the user.
- 3Check the language data in Tools for the date display convention tied to that language.
- 4In the Web UI check the browser language and regional settings, because the front end may format dates independently.
- 5For reports, open the report in the report designer and check whether the date is formatted by a field setting or by a hard-coded mask.
- 6Re-test with a new login, since many settings are read when the session starts.
Display versus stored value
LN stores dates and times as values and formats them for display. A date format change therefore never changes data, which is also why a wrong-looking date is almost always a display layer problem. Do not edit stored data to fix a format.
Be careful with date and time zone: LN holds UTC values for date-time fields and converts to the user's time zone for display, so a date can appear to shift a day when a user in another time zone views a late-evening timestamp.
Reports and exports
Reports can override the display, either by a format mask or by building the date as text. If one report differs from the screen, the report is the cause. Exports to Excel carry the value and the formatting of the receiving application, so a day and month swap in Excel usually comes from Excel's regional settings.
Integrations and BODs
Never exchange dates as locale-formatted text. BODs and APIs use ISO 8601 style values. If a partner system sends dd/mm/yyyy, convert at the boundary in the mapping and document the rule. The classic failure is 03/04 read as March 4 on one side and April 3 on the other.
ISO 8601 date: 2026-04-03 ISO 8601 date-time: 2026-04-03T14:30:00Z
Try it here, free
Infor LN User Access Review Checklist
A practical checklist for periodic review of who can do what in Infor LN, covering roles, privileged access and segregation of duties.
Common pitfalls
- !Fixing a display problem by editing stored data.
- !Assuming the Web UI follows the LN user setting when it follows the browser locale.
- !Passing locale-formatted text through integrations.
- !Ignoring the UTC conversion on date-time fields.
How an ERP-grounded AI assistant handles this
A grounded assistant can answer which date convention a given user, report or interface uses, and can spot an integration mapping that converts dates incorrectly. It reads configuration and logs, and any change to mappings still goes through your change control.
Frequently asked questions
Is there one global date format setting in Infor LN?
No. The format depends on the user's language and locale settings, the Web UI browser, and report layouts. Check each layer in that order.
Why do dates look different in Excel exports?
Excel applies its own regional settings to the exported value. The LN value is unchanged. Fix the Excel locale or export in ISO format.
What format should integrations use?
Use ISO 8601 for dates and date-times, in UTC for timestamps, and convert at the boundary of any system that needs a local format.
Does changing the format change existing data?
No, only the display. The stored value is the same before and after.
Related
Infor M3 Date Format: User Setting, API and Database
M3 stores and exchanges dates as 8-digit numbers in year-month-day order, for example 20261021. What a user sees on a panel follows the date format set on their user record, but the database and MI APIs do not change with it. Convert at the edges of an integration and never rely on the display format.
How-toInfor LN integration document types and integration rules with ION
In LN, an integration document type ties an LN business object to a BOD noun and direction so ION can send or receive it. Rules and mappings then decide which LN data populates the BOD, which events trigger publication and how incoming BODs are converted into LN transactions. Set up the document type first, then the mapping, then test in ION Desk.
How-toInfor LN Report Designer: How to Build and Personalize Reports
Infor LN reports are designed in LN Studio's report designer, where a report is defined by its input fields, data selection through the session's tables and a layout of sections. To personalize a standard report, copy it into your customer VRC and edit the copy, never the standard object, so upgrades do not overwrite your work.
Error fixInfor LN bshell Process Stuck at 100% CPU: How to Diagnose and Fix It
A bshell process pinned at 100% CPU on the Infor LN application server almost always means one session is stuck in a 4GL loop, scanning an unindexed table, or waiting on a database lock. End the session from the Sessions Monitor first, then kill the OS process only if that fails, and check for a blocking database transaction before assuming it is a bug.
Error fixInfor LN Not Authorized to Run This Session: How to Fix It
Infor LN refuses to open a session with a not authorized message when the logged-in user's assigned role does not include that session, or when the session is blocked for the company they are logged into. Grant the session through Common > Authorization Management > Roles, or check the user's role and company context, and the session opens on retry. In most cases this is a permissions configuration issue, not a bug.
Error fixInfor LN DAL Out of Sync After a Custom Field: Cause and Fix
Infor LN throws a DAL, or table, out of sync error, or simply drops a new custom field silently, when a table's dictionary definition is changed but the generated DAL and dependent forms are not regenerated afterward. Running the standard sequence, table compile, DAL generation, then session/form compile, in Tools > Development after every dictionary change resolves it. Skipping any one of the three steps is what causes the mismatch.
AI for ERPAI for Infor LN: Sessions, BODs, and Engineer-to-Order Work
Add grounded AI to Infor LN 10.x or CloudSuite: natural-language answers over sessions and BODs, agents for project and engineer-to-order work, on-prem options.
AI for ERPInfor M3 AI: A Practical Path from MI Programs to a Private Assistant
Infor M3 AI explained: grounded natural-language answers over MI programs and MEC, agents for distribution and manufacturing, on-prem or EU private cloud.
Stuck on Infor LN?
Talk to engineers who work inside Infor LN every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- Infor LN User Access Review ChecklistA practical checklist for periodic review of who can do what in Infor LN, covering roles, privileged access and segregation of duties.
- Infor LN Change Request Form TemplateFill-in change request form for LN and Baan changes, covering scope, impact, testing, rollback and sign-off.
- Infor LN User Role and Authorization Matrix WorksheetRole-by-function matrix for LN access reviews, with access level, risk rating and segregation of duties flags.
ERP fixes and how-tos
- Format Codes in Infor LN: Data Formats and MasksWhat format codes and display formats mean in Infor LN, how domains use them to show numbers, dates and codes, and how to change a format without breaking data.
- How to Create an Infor LN User from a User Template and Copy AuthorizationsCreate Infor LN users from user templates and roles, copy authorizations safely, and avoid the common mistakes that give new users too much or too little.
- Infor LN Inbound BOD Mapping and DescriptionsWhat a BOD is, the full form, how Infor LN receives inbound BODs through ION, how integration document types and mapping work, and how to read the fields.
Runs with your ERP
- XEDI EDI Integration with Infor LN (ION BODs)How XEDI translates X12 and EDIFACT into Infor BODs routed through ION for Infor LN, plus SyteLine and M3. Setup steps, data flows, pitfalls and FAQ.
- SIGMA MES and Infor LNSIGMA MES from a certified Infor LN partner in Germany: how it connects to Infor LN, Infor OS/ION and web services, setup, pitfalls, alternatives and AI uses.
Guides
- Infor LN UI Modernization OptionsInfor LN UI options compared: LN Web UI, Ming.le homepages, custom portals and mobile, with a tiered plan by user type to modernize the LN interface.
- Infor LN API Development: REST, SOAP, and BOD Integration GuideBuild integrations with Infor LN APIs using BODs, web services, and the LN Integration Framework. Developer guide for LN REST and SOAP endpoint programming.
- Infor LN Printing and Report Design GuideDesign Infor LN reports and configure printing. Report session development, document output, label printing, and Crystal Reports integration for LN.
AI on your ERP
- AI for Infor LN: Sessions, BODs, and Engineer-to-Order WorkAdd grounded AI to Infor LN 10.x or CloudSuite: natural-language answers over sessions and BODs, agents for project and engineer-to-order work, on-prem options.
- AI for Infor LN in Aerospace and Defense ManufacturingAI grounded on Infor LN project, contract, and configuration management data for aerospace and defense manufacturers, with on-prem deployment for ITAR.
Integrations
- How to add AI agents to Infor LNHow to add AI agents to Infor LN: a tool layer over ION API and BODs, read-only reporting first, approval before writes, and fully on-prem model hosting.
- How to add an AI chatbot to Infor LNHow to add an AI chatbot to Infor LN for planners, buyers and customers, grounded in ERP data and documents, deliverable inside Infor OS or a portal, and runnable on-prem.