# What Customizations Are Allowed in CloudSuite Industrial Multi-Tenant? > Source: https://netray.co/erp-help/csi-multi-tenant-customization-what-is-allowed > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer In the multi-tenant cloud edition of CloudSuite Industrial (SyteLine), customers work through configuration and supported extension points: form customization, user-defined fields, the event system, custom reports, and integration through ION and the IDO REST service. Anything that needs deploying your own server-side binaries or touching the database directly is generally restricted because the infrastructure is shared. Confirm exact limits for your tenant with Infor, since they change by release. ## Kind advanced ## System syteline ## Erp Infor CloudSuite Industrial (SyteLine) Multi-Tenant ## Module Extensibility / Mongoose ## Query what customizations are allowed in CloudSuite Industrial multi-tenant ## Alternate Queries - SyteLine multi-tenant cloud customization limits - can I use extension classes in CloudSuite Industrial multi-tenant - CSI multi-tenant vs single-tenant customization - SyteLine cloud extensibility options ## Applies To Infor CloudSuite Industrial (SyteLine) multi-tenant cloud on Infor OS; contrast with single-tenant cloud and on-premises SyteLine 9.x/10.x ## Steps ### How to plan customizations for a multi-tenant tenant **Items:** Inventory every existing customization: forms, user-defined fields (UDFs), custom IDOs, extension classes, event handlers, SQL views, SSRS or custom reports, and external integrations. Classify each as configuration (forms, UDFs, event actions, user-defined tables), custom code (IDO extension class, custom .NET assemblies), or direct database dependency (SQL views, stored procedures, ODBC reports). Ask Infor or your partner in writing which of those categories your specific tenant tier supports, and keep the reply with the project record. Re-implement configuration items first using Form Editor, UDFs and the Event System, because they travel with the tenant and survive upgrades. Move logic that needs real code outside the tenant: build it as an external service that calls the ION API and IDO REST endpoints, authenticated with an ION API service account. Replace direct SQL reporting with supported data access: IDO-based reports, Infor reporting tools, or data lake extracts (see the related reporting page). Test in a non-production tenant and run the full regression before promoting, since Infor updates multi-tenant on a vendor-managed schedule. ## Sections ### Why multi-tenant changes the rules **Body:** On-premises and single-tenant SyteLine let you deploy extension class assemblies to the application server, create SQL views and call stored procedures directly. That freedom depends on you owning the server and database. In multi-tenant, many customers share application infrastructure that Infor operates and updates on its own cadence, so a customer-supplied DLL or an ad hoc database object is a risk to every other tenant and to the upgrade process. The practical result is a split. Things that are data or metadata (form definitions, UDF definitions, event configuration) are stored in the tenant's configuration and are fine. Things that are executable code on shared servers, or direct access to the underlying SQL Server, are limited or unavailable. The exact boundary differs by contract and release, so treat any list, including this one, as a starting point to verify. ### What generally remains available **Body:** Mongoose form customization stays the main lever: add fields, rearrange layouts, set validation and form-level scripting within what the tenant allows. User-defined fields extend core tables without schema changes you manage yourself. The Event System (events, event handlers and actions) lets you react to IDO or form events with configurable actions such as setting values, sending notifications or invoking supported methods. Integration is the other big channel. The IDO REST service exposed through the ION API gateway lets an external application read and write business objects with the same business rules as the UI. ION also gives you BODs and workflows for system-to-system flows. If you need heavy logic, the usual pattern is an external service you host, calling these endpoints. ### What typically needs a redesign **Body:** Extension classes written in C# that run inside the application server are the biggest migration item. Where the tenant does not accept them, move the logic to an external service, or replace it with event actions and form scripts if the logic is small. Expect to re-test transaction boundaries, because an external call is no longer inside the same database transaction as the IDO save. Custom SQL views, stored procedures and ODBC-based reports usually depend on direct database access, which shared tenants generally do not expose. Rebuild them as IDO-based reports, as extracts into the Infor data lake, or as reports through supported reporting tools. Inventory these early, because they are often undocumented and owned by finance or operations rather than IT. **Code:** # Read items through the ION API gateway (shape of the call; tenant and base URL come from your .ionapi file) GET https:////CSI/IDORequestService/ido/load/SLItems?properties=Item,Description,UM&filter=Item%20LIKE%20'A%25'&rowcap=50 Authorization: Bearer ### Decision rule: configure, integrate, or move tenancy **Body:** A simple rule works well. If a requirement can be met by form, UDF or event configuration, do it there. If it needs code, ask whether it can run outside the tenant and talk to ION and IDO REST. If it needs deep server-side code or database access and the business case is strong, the answer may be a different deployment model such as single-tenant cloud, which Infor positions for heavier customization, or removing the requirement. Do not decide by assumption. Contract tier, release and the specific feature matter, and Infor's documentation for your release is the authority. Write down the answer for each customization so the next upgrade review does not repeat the investigation. ## Pitfalls - Assuming a customization that worked on-premises will be accepted in multi-tenant without asking; extension classes and database objects are the usual blockers. - Treating external services as free: moving logic outside the tenant removes the shared database transaction, so you must handle retries and partial failures yourself. - Leaving direct SQL reports for last; they often have no documented owner and surface only at cutover. - Putting secrets for the ION API service account in scripts or form code instead of a managed secret store. - Skipping regression after vendor-managed updates; configuration can still be affected when a form or IDO changes. ## Ai Angle An AI assistant grounded in the tenant can help with the inventory step: reading form customizations, UDF definitions and event configuration through supported interfaces, and classifying each as configuration, code or database dependency. SyteRay is built for this kind of SyteLine customization and upgrade analysis, and any generated change is proposed for human review rather than applied automatically. It does not change what Infor permits in your tenant. ## Faq ### Can I deploy my own extension class DLL in multi-tenant? **Answer:** Generally no, because the application servers are shared and operated by Infor. Customer-supplied server-side assemblies are the main thing that restricted tenants avoid. Check your contract and release with Infor. The common alternative is to host the logic as an external service that calls the ION API and IDO REST endpoints. ### Are user-defined fields supported in multi-tenant? **Answer:** Yes, UDFs are part of the configuration layer and are the standard way to extend core tables without managing schema changes yourself. They appear on forms through Form Editor and are available to the event system and reports. Verify any limits on count or data type for your release. ### Can I still run SQL reports against the database? **Answer:** Direct database access is generally not available on shared tenants. Plan to rebuild such reports using IDO-based reporting, Infor reporting tools or extracts into a data lake. Confirm with Infor what read access, if any, your agreement includes. ### Is single-tenant cloud the answer to heavy customization? **Answer:** It is the option Infor generally positions for more customization, because you get a dedicated environment. It is not automatically better: you also take on more change management. Compare the cost of re-engineering the customization against the cost of the heavier deployment model. ## Search terms CloudSuite Industrial multi-tenant customization, SyteLine multi-tenant extension class, CSI multi-tenant vs single-tenant, SyteLine cloud customization limits, Mongoose form customization cloud, SyteLine UDF user defined fields, ION API IDO REST SyteLine, SyteLine cloud migration customizations --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json