How-toInfor LNTools / Studio

Infor LN Application Studio and Studio: overview and getting started

Question
infor ln application studio

Also searched as

  • infor ln studio getting started
  • infor ln customization tools
  • infor ln application customizing

Short answer

LN customization is done with the LN Studio development tool and the application customization features of the LN UI. Studio is used to create or change sessions, forms, reports, scripts and DAL logic, kept in a customer VRC so standard code is untouched. Start with a development environment, a customer VRC and a small change.

Applies to: Infor LN 10.x. Tool names and the exact customization features vary by release.

Get started safely

  1. 1Get a development environment that mirrors production, with a developer license and developer authorizations.
  2. 2Create or confirm a customer VRC derived from the standard one, and a package combination for developers.
  3. 3Open LN Studio and connect to the development environment, selecting the customer VRC.
  4. 4Make a small change first, such as adding a field to a form, and test it in the LN UI.
  5. 5Use DAL extensions for business rules rather than editing standard scripts.
  6. 6Move changes through your normal path to test and production using the standard transport or export/import process, with a change record.

What you can change

Typical changes are custom fields on standard tables, forms, zoom links, reports, DAL hooks for validation and defaults, and entirely new sessions for local processes. LN also offers UI-side personalization for fields and layouts that do not need development.

Prefer configuration and personalization first, then DAL extensions, then standard-script changes only as a last resort. Each step up increases upgrade cost.

VRCs and upgrade safety

A VRC (version, release, customer) layers your changes over the standard one. Because your objects live in a separate VRC, an upgrade replaces the standard layer and you re-test the customizations. The less you override, the cheaper the upgrade.

Keep a register of customizations with an owner and a business reason. It is the first thing an upgrade project asks for.

Where to continue

See the related pages on creating a custom session, compile errors and DAL custom field sync for step-by-step detail.

Try it here, free

Infor LN and Baan Customization Inventory Worksheet

Open full tool

Editable worksheet to list every Baan or LN customization with type, owner, effort and a retire, keep or replace decision.

Common pitfalls

  • !Developing directly in production.
  • !Editing standard objects instead of the customer VRC.
  • !No customization register.
  • !Skipping DAL extensions and hiding rules in UI scripts.
  • !Forgetting to regenerate the runtime data dictionary after table changes.

How an ERP-grounded AI assistant handles this

Netray's SyteRay-style agents for developers read an existing customization set, explain what each customized object does and draft DAL or script changes for review. For LN, the same private, on-prem approach applies: models run on your hardware and your source stays inside.

Frequently asked questions

Is LN Studio the same as Application Studio?

Names have shifted between releases and documentation. Studio is the developer tool for sessions, scripts and DAL. Check your release's documentation for the exact customization features in the UI.

Do I need a developer licence?

Yes, development tooling generally requires one. Confirm with your Infor contract.

Will customizations survive an upgrade?

Those in a customer VRC are retained but must be re-tested and sometimes adapted to changed standard objects.

Where do I start for a new custom session?

Follow the create custom session guide, then add DAL logic only if rules are needed.

Related

Advanced

How to create a custom session in Infor LN Studio

Infor LN Studio's session designer generates a new maintenance, overview or detail session from a table definition, then lets you arrange fields, attach DAL2 validation, and wire menu access, all inside a custom package so the session survives upgrades. Building on a custom table gives the lowest upgrade risk; extending a standard table needs more care and re-testing after every release.

Error fix

Infor LN Studio: compile errors when building DAL/4GL code

A compile error in LN Studio usually traces back to a missing or mismatched package reference, a real syntax error in the DAL or 4GL source, or stale generated metadata that only a full rebuild clears. Read the first error in the log, not the last, since later errors are often cascades from one root cause.

Error fix

Infor 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.

Advanced

How to extend business logic in Infor LN with DAL2

DAL2 lets you add custom validation, defaulting and calculation logic to Infor LN Enterprise Edition tables by writing a Java business logic handler class and registering it against a table event, without editing the standard DAL. Because the logic sits in your own package rather than inside Infor's base code, it survives upgrades that would otherwise overwrite a direct DAL change.

Error fix

Infor 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 fix

Infor 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.

AI for ERP

AI 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 ERP

AI for Legacy Baan IV/V: Capture the Knowledge Before It Walks Out the Door

Use AI to capture knowledge from ageing Baan IV/V systems, document undocumented customisations, and de-risk a future migration to LN or CloudSuite.

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

ERP fixes and how-tos

Guides

Integrations

Software