SyteLine Form Personalization: The Right Way to Change Forms
SyteLine form personalization is the ability to modify form layouts, fields, captions, and behavior through layered metadata - at the user, group, or site level - without changing Infor's vendor form definitions. The Mongoose form engine stores each form as a stack of versions: vendor baseline, site customizations, and user personalizations, merged at load time. Done correctly, changes survive upgrades and stay auditable; done wrong, they create a thicket of conflicting layers that makes every upgrade a forensic exercise. This guide explains the layers, the editing modes, and the governance that keeps hundreds of modified forms manageable.
Personalization vs Customization: Understanding Form Layers
The distinction matters more than any other concept in SyteLine form work. A personalization is a user-scope change - hiding a column, reordering fields, saving a default filter - stored against that user and invisible to everyone else. A customization is a site-scope change made in design mode that alters the form for all users, stored as a site version layered over the vendor definition. At load, the engine merges vendor, then site, then user layers. Upgrades replace only the vendor layer, and FormSync reconciles your site layer against it - which is why disciplined shops keep customizations minimal and push cosmetic preferences down to personalizations where they cannot block an upgrade.
Making Changes in WinStudio Design Mode
Site-level customization happens in design mode, entered from the runtime with the appropriate edit level. From there the toolbox lets you add components bound to IDO properties, adjust tab order, set validators, and attach scripts.
- Open forms in design mode with site edit level to create site versions, not accidental user versions
- Bind new components to existing IDO properties or user-defined fields rather than unbound variables where possible
- Use component-level Enabled/Visible expressions instead of scripts for simple conditional behavior
- Save with a change description every time; the form version history is your only built-in audit trail
Upgrade-Safe Practices and FormSync
Every site customization is a future FormSync decision. When Infor ships a new vendor form version, FormSync compares it against your site layer and auto-merges non-conflicting changes; conflicts - the vendor moved a component you also moved - queue for manual resolution. Shops with 300-plus customized forms routinely spend 4-8 weeks of an upgrade purely on FormSync reconciliation. The mitigation is hygiene: retire unused customizations annually, never customize a form to do what a personalization or DataView could, prefer new custom forms over heavily rebuilt vendor forms, and document why each change exists. Teams that follow this reduce upgrade form-remediation effort by half or more.
Governance: Who Changes What, and How You Know
Uncontrolled form editing is how ERP environments rot. A working governance model is lightweight but explicit, and it is enforceable with SyteLine's own edit levels and permissions.
- Restrict design-mode (site edit level) rights to a named group of 2-3 administrators
- Log every site customization in a register: form, date, author, business reason, linked ticket
- Review user personalizations before upgrades; stale ones cause confusing merged layouts
- Promote form changes dev to pilot to production with metadata export, never by re-keying
How Netray Brings AI to Form Governance
Netray's form-audit agents read your forms database directly and produce what no manual process sustains: a living inventory of every site version, user personalization, and attached script, with each change classified as cosmetic, functional, or upgrade-risky. Before a CloudSuite Industrial migration, one aerospace machining client had Netray analyze 412 customized forms; the agent flagged 138 as retirable and pre-classified the FormSync conflict risk of the rest, cutting the form remediation phase from a projected 9 weeks to 4. Agents run entirely on-prem against the forms database, so ITAR-restricted environments get full analysis with zero data egress.
Frequently Asked Questions
What is the difference between personalization and customization in SyteLine?
A personalization is a user-level change - hidden columns, field order, saved filters - stored per user and invisible to others. A customization is a site-level change made in WinStudio design mode that alters the form for all users. The form engine merges vendor, site, and user layers at load time. Customizations must be reconciled by FormSync during upgrades, while personalizations rarely block anything, so prefer the lightest layer that meets the need.
Do SyteLine form customizations survive upgrades?
Site customizations are preserved as a separate layer, and FormSync merges them against the new vendor form versions during an upgrade. Non-conflicting changes merge automatically; conflicts where Infor changed the same components you did require manual resolution. Environments with several hundred customized forms typically budget multiple weeks for FormSync reconciliation, which is why minimizing and documenting site customizations is the core upgrade-safety practice.
How do I add a field to a SyteLine form?
First add the data element - a user-defined field or user extended table column - so there is an IDO property to bind. Then open the form in design mode at site edit level, drag the appropriate component from the toolbox, bind it to the IDO property, set its caption and tab order, and save the site version with a change description. Test in a non-production configuration and promote via metadata export rather than re-keying in production.
Key Takeaways
- 1Personalization vs Customization: Understanding Form Layers: The distinction matters more than any other concept in SyteLine form work. A personalization is a user-scope change - hiding a column, reordering fields, saving a default filter - stored against that user and invisible to everyone else.
- 2Making Changes in WinStudio Design Mode: Site-level customization happens in design mode, entered from the runtime with the appropriate edit level. From there the toolbox lets you add components bound to IDO properties, adjust tab order, set validators, and attach scripts..
- 3Upgrade-Safe Practices and FormSync: Every site customization is a future FormSync decision. When Infor ships a new vendor form version, FormSync compares it against your site layer and auto-merges non-conflicting changes; conflicts - the vendor moved a component you also moved - queue for manual resolution.
Put this into numbers
Free interactive tools for exactly this problem. No signup to use them.
SyteLine Customization Technical Debt Scorer
Measure how much upgrade drag, risk, and maintenance cost your SyteLine customizations have accumulated, and learn where to pay it down first.
Free ToolSyteLine Implementation Cost Calculator
Estimate the full first-year cost of an Infor SyteLine implementation, including licensing, services, data migration, and internal effort.
Free ToolSyteLine to CloudSuite Upgrade Cost Estimator
Estimate what it will cost to move from your current SyteLine version to CloudSuite Industrial, including customization remediation and integration rework.
Terms used in this article
Get a Netray form-layer audit before your next SyteLine upgrade and know exactly which of your customizations will merge, conflict, or can simply be deleted.
Related Resources
The SyteLine Mongoose Framework: A Developer Guide
Complete developer guide to the SyteLine Mongoose framework: IDOs, WinStudio forms, application events, and scripting in Infor CloudSuite Industrial.
Infor SyteLineSyteLine DataViews: Reporting Without a Developer
Build SyteLine DataViews reports without a developer: DataView setup, subcollections, publishing to users, filters, and Excel export in CloudSuite Industrial.
Infor SyteLineSyteLine Event System: Automating Workflows
Automate workflows with the SyteLine event system: event definitions, handlers, actions, approval routing, and how to troubleshoot stuck events explained.