# How to create a custom session in Infor LN Studio > Source: https://netray.co/erp-help/ln-studio-create-custom-session > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer 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. ## Kind advanced ## System infor-ln ## Erp Infor LN ## Module LN Studio / Session Designer ## Query how to create a custom session in infor ln studio ## Alternate Queries - infor ln studio new session tutorial - build custom maintenance session infor ln - infor ln session designer guide - add custom table and session infor ln ## Applies To Infor LN Enterprise Edition, Infor LN Studio (Eclipse-based IDE) ## Steps ### Build and deploy a custom session in LN Studio **Items:** - Launch Infor LN Studio and open, or create, a custom development package linked to your VRC. - If the session needs a new custom table, define it first: fields, keys and indices, inside the custom package. - Use the session designer to generate a new session against the table, choosing the session type: maintain, overview, detail or specific. - Arrange the generated form: group fields, set tab order, add choice fields, and attach any DAL2 business logic handlers needed for validation. - Set session properties: title, authorization group, help text, and whether the session is a maintenance or read-only overview. - Compile the package and correct any generation or reference errors reported by LN Studio. - Add the session to a menu entry so users can reach it, and assign the correct authorization group. - Deploy to a test VRC, log in as a test user, and run the session end to end: create, change and delete where applicable. - Promote through acceptance to production following your standard change control, and log the session in your customization register. ## Sections ### What LN Studio actually generates **Body:** LN Studio produces a session's form definition and default data-handling logic straight from the table metadata, which saves you from hand-coding the UI layer field by field. You then customize the layout, attach DAL2 handlers for anything beyond basic create, change, delete and query behavior, and connect the session to a menu. This model-driven approach is why LN Studio sessions stay consistent with the look and behavior of standard LN sessions: the generator applies the same form patterns Infor's own sessions use. ### Custom tables vs extending standard tables **Body:** Building a session on a brand-new custom table is the lowest-risk path: nothing about it depends on how Infor structures its own tables, so upgrades rarely touch it. A session that surfaces a standard table with extra custom fields needs the field added through a table extension in your custom package, then referenced from the session. This carries more upgrade risk, because a base table's structure, field names or positions can change between releases, so re-test that session every upgrade rather than assuming it still compiles cleanly. ### Authorization and menu placement **Body:** Assign a proper authorization group to every custom session; skipping this leaves a maintenance session reachable by anyone with generic access. Put the new entry under a custom menu rather than a standard one where possible, since standard menus can be reorganized by Infor on the next upgrade, which quietly breaks navigation paths users had bookmarked or memorized. ### Testing before promotion **Body:** Test the session against data volumes closer to production than a handful of sample records, since a missing index or an inefficient query in the generated overview session often only shows up under real row counts. Confirm any DAL2 validation attached to the session actually fires for every relevant path, including edge cases like deleting a record that has dependent data, before promoting the package beyond your test VRC. ## Pitfalls - Building the custom session directly inside a standard Infor package instead of your own custom package. - Skipping authorization group assignment, leaving a sensitive maintenance session open to any user with generic access. - Testing only with a handful of sample records, so a slow query or missing index only surfaces after go-live. - Placing the new session under a standard menu that gets reorganized on the next LN upgrade, breaking navigation. - Referencing standard table fields without planning to re-test the session on every future upgrade. - Not documenting the custom session in the customization register, so nobody remembers why it exists two upgrades later. ## Ai Angle Once a custom LN Studio session and its table are described to a grounded AI agent, it can answer support questions about what the session does without a separate document being written, and it can flag when a proposed new field name collides with an existing standard table column before you generate the session, catching the conflict at design time instead of at compile time. ## Faq ### Does LN Studio require Eclipse? **Answer:** Yes. Infor LN Studio is delivered as a set of plugins on the Eclipse IDE, so you develop DAL2 logic, table definitions and sessions inside that Eclipse-based workspace connected to your LN Enterprise Edition environment. ### Can I build a custom session without writing any DAL2 code? **Answer:** Yes, for simple maintain or overview sessions on a custom table, since LN Studio generates standard create, change, delete and query logic automatically. You only need DAL2 code for validation, defaulting or calculated fields beyond that generated baseline. ### Will a custom session survive an Infor LN upgrade? **Answer:** A session built in its own custom package on a custom table usually survives cleanly. A session that references standard table fields needs re-testing every upgrade, because Infor can change those fields' names, types or positions. ### How is a custom session different from personalizing a standard one? **Answer:** Personalization changes how an existing standard session looks or behaves for a user or role, using the session's own runtime personalization tools. Building a custom session in LN Studio creates a brand-new session backed by its own logic and, usually, its own table. ## Search terms infor ln studio, create custom session infor ln, infor ln session designer, infor ln custom table, infor ln eclipse ide, build maintenance session infor ln, infor ln session wizard, infor ln customization package, infor ln enterprise edition development, baan ln studio tutorial --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json