SyteLine Mongoose Customization Deployment Checklist
This checklist promotes Mongoose customizations in SyteLine 9 and CSI 10 from development to test to production in the order dependencies require. It covers WinStudio forms, IDO metadata, extension class assemblies, SQL objects, events, background tasks and reports.
0 of 28 items complete
9 critical items still open - these are the highest-risk gaps.
Forms
IDO metadata
Extension classes
SQL objects
Events
Background tasks and reports
Verification and rollback
A deployment is ready when every critical item is ticked in the target environment, not in development. Missing event global constants and an unchanged assembly version are the two most common reasons a promotion looks complete but behaves like the old build.
Get a deployment package review
Send us your object list for the next release and we will check the order and the rollback plan against your SyteLine version.
Optional. The tool and every export work without this. No spam.
How to use it
Copy the checklist once per release package and export it with the package. Work through groups in the order shown, because the order follows dependencies: database columns before IDO properties, IDO metadata before forms that bind to it, assemblies before IDOs that reference them, constants before event handlers that read them. Run it first for development to test, then again unchanged for test to production. If something had to be fixed by hand in test, it goes back into the package before production.
Where this lives in Mongoose
IDO definitions move with App Metadata Transport, which exports metadata to XML and imports a previously exported file. Extension class assemblies are loaded on the IDO Custom Assemblies form, and each IDO points at its assembly through the Custom Assembly Name and extension class fields on the IDOs form. Forms and global objects live in the forms metadata at site, group or user scope. Events, handlers and actions are maintained on the Events and Event Handlers forms, with run results on Event Status and Event Handler Status.
- App Metadata Transport: IDO metadata XML export and import
- IDO Custom Assemblies: extension class DLLs
- Event Handlers: handler settings and sequence
- LogMonitor: runtime errors during smoke tests
Version differences and gotchas
Updates can change standard stored procedures, so an EXTGEN_ override that matched the old signature can fail after an update even though nothing in your package changed. Field labels and the exact export method for forms vary between SyteLine 9 and CSI 10 builds, so record which tool you used in the deployment notes. Customizations saved at user scope by a developer are invisible in testing under other logins and get missed. Event global constants often hold environment specific values and must be edited after import.
How to check the result in the system
Open each changed form as a normal user in the target and run the scenario the change was built for. Keep LogMonitor open to catch IDO and extension class errors as they happen. Check the assembly version loaded matches the build you tagged. Trigger each new event and look at Event Status for its result. File the exported checklist with the change record.
Frequently Asked Questions
What is the Infor Mongoose platform?
Mongoose is Infor's application framework that SyteLine and CSI are built on. It provides IDOs (business objects over SQL tables and stored procedures), WinStudio forms, the event system, background task processing through TaskMan, and the IDO request service that REST and SOAP clients call. Customizations are layered on top through metadata, extension classes and SQL.
How do I move IDO changes between environments?
Export the changed IDOs from the source with App Metadata Transport, which writes an XML file, then import that file with App Metadata Transport in the target. Import works only from a previously exported file. Deploy any database columns the IDO properties bind to first, and load extension class assemblies before the IDOs that reference them.
Why does my new extension class not run after import?
Usual causes: the IDO still points at the old assembly or class name, the IDO runtime has not reloaded metadata, or the assembly built is not the version you think. Check Custom Assembly Name and the extension class fields on the IDOs form, raise the assembly version on every build, and recycle the IDO runtime.
Should user fields go before or after IDO metadata?
Before. User defined fields and user extended tables create database columns that IDO properties and form components bind to. If the IDO metadata arrives first, properties point at columns that do not exist yet and loads fail. Apply SQL and user field changes, then IDO metadata, then assemblies, then forms and events.
If you want an AI assistant that reads your SyteLine customizations and drafts the deployment list for each release on your own servers, we can set that up.
Related Tools
SyteLine Event System Troubleshooting Checklist
Checks for event handlers in SyteLine 9 and CSI 10 that do not fire, fire twice or hang, from event name and flags to runtime services and action outcomes.
Developer ToolsSyteLine IDO API Security Hardening Checklist
Accounts, transport, tokens, request hygiene and monitoring checks for exposing the SyteLine IDO request service (REST and SOAP) to integrations and scripts.
Infor SyteLineSyteLine 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.
Infor SyteLineSyteLine Upgrade Regression Test Checklist
A practical regression checklist for SyteLine upgrades across business processes, customizations, reports and integrations.
Developer ToolsSyteLine Custom Table CREATE Script Generator
Creates a SQL Server CREATE TABLE script for a custom SyteLine table that follows the standard column and key conventions.
More Developer Tools tools
See all- SyteLine IDO REST Request Generator
- SyteLine SQL Query Generator for Item, Job and Order Tables
- SyteLine SQL Blocking and Long Running Query Script Generator
- SyteLine Mongoose Framework Events Reference
- SyteLine Event Action Types Reference
- SyteLine Event Action Parameter Functions Reference
- SyteLine WinStudio Standard Form Events Reference
- SyteLine Mongoose API Options Reference
- SyteLine SQL User-Defined Data Types Reference
Keep exploring
Free tools
- SyteLine Mongoose API Options ReferenceA side-by-side reference of the Mongoose interfaces for SyteLine 9/10 and CSI: endpoint, authentication, operations, best use and the traps in each.
- SyteLine Mongoose Framework Events ReferenceEvery framework event an application event handler can subscribe to in SyteLine 9/10 and CSI on-prem, with when it fires, what it passes and the traps to avoid.
- SyteLine Mongoose .NET Client GeneratorGenerate an external C# program that logs on through the Mongoose .NET client library and loads SyteLine IDO data, with custom load and nested load options.
ERP fixes and how-tos
- How to Add Custom Business Logic to a SyteLine IDO with an Extension ClassAdd custom validation to a SyteLine IDO without touching generated code: extension class structure, BeforeAdd/AfterModify events, and deployment steps.
- What Customizations Are Allowed in CloudSuite Industrial Multi-Tenant?What you can and cannot customize in CloudSuite Industrial multi-tenant: forms, UDFs, events, reports, ION and REST, and what to do when code is restricted.
- How to Debug a SyteLine IDO Extension Class in Visual StudioBreakpoints not hitting in a SyteLine IDO extension class? Here is how to attach Visual Studio to the right process, load matching PDBs, and debug it.
Guides
- How to Set Up SyteLine Mongoose IntegrationGuide to integrating Infor Mongoose framework with SyteLine CloudSuite Industrial. Learn form development, IDO extensions, event scripting, and deployment configuration.
- SyteLine .NET Customization Patterns and Best PracticesMaster SyteLine .NET customization patterns. IDO extensions, form scripts, assembly deployment, and upgrade-safe development practices for developers.
- SyteLine Mongoose IDO Development GuideMaster SyteLine IDO development with Mongoose. IDO architecture, custom methods, stored procedures, and IDL best practices for CloudSuite Industrial.