Infor SyteLineFree referencePDF, Excel, Word exportInfor SyteLine

SyteLine IDO Names Reference: SLItems, SLJobs, SLCos and More

In SyteLine, forms, reports and external integrations reach data through IDOs, the business objects of the Mongoose framework. This lookup maps commonly used IDO names to the tables behind them, so you can find the right object quickly when building an integration or a form.

Download:

IDO name	Underlying table	Area	Typical use
SLItems	item_mst	Inventory	Read or maintain the item master
SLItemWhses	itemwhse_mst	Inventory	On hand and planning data by warehouse
SLWhses	whse_mst	Inventory	Warehouse list for pick lists and filters
SLLots	lot_mst	Inventory	Lot lookups and traceability queries
SLMatltrans	matltran_mst	Inventory	Inventory transaction history reads
SLProdcodes	prodcode_mst	Inventory	Product code lookups
SLJobs	job_mst	Production	Job header reads and updates
SLJobRoutes	jobroute_mst	Production	Job operations and status
SLJobmatls	jobmatl_mst	Production	Job material requirements and shortages
SLWcs	wc_mst	Production	Work center lookups
SLCos	co_mst	Sales	Customer order headers
SLCoitems	coitem_mst	Sales	Customer order lines and due dates
SLCustomers	customer_mst	Sales	Customer master reads
SLPos	po_mst	Purchasing	Purchase order headers
SLPoItems	poitem_mst	Purchasing	Purchase order lines and receipts
SLVendors	vendor_mst	Purchasing	Vendor master reads

IDO names are conventions that vary by release and by customer extensions. Confirm the exact name and property list in the IDOs form of your own system before coding against it.

Need an inventory of your SyteLine integrations?

An optional review that lists which IDOs and tables your external systems touch, and where service accounts are over permissioned.

Optional. The tool and every export work without this. No spam.

How to use this reference

Search by table name when you know the data, or by IDO name when you are reading a request. Once you have the IDO, open the IDOs form in your system to see the real property list, then build your request. Over REST, the load pattern is a GET to the IDORequestService with the IDO name, a comma separated property list, an optional filter and a row cap. Keep the property list short, because loading all properties is slow and returns data you do not need.

Look up the table, then confirm the IDO in the IDOs form
Request only the properties you need
Always set a row cap when testing

IDOs versus direct SQL

IDOs enforce security, run event handlers and respect the site context, which is why integrations should prefer them over direct SQL. Direct SQL is faster to write but can expose data across sites, skip validation and break on upgrade if table structures change. A pragmatic split is IDOs for any write and for external system access, and read only SQL for internal reporting and diagnostics.

Common mistakes

Developers often hardcode IDO property names copied from another environment, then discover the customer's release or custom extensions differ. Others forget that IDO requests run as a user, so a service account without the right permissions returns empty results rather than an obvious error. Test integrations with the same account and configuration they will use in production.

Frequently Asked Questions

What is an IDO in SyteLine?

An IDO, or Intelligent Data Object, is a business object in the Mongoose framework that exposes properties and methods over one or more tables. Forms, reports, workflows and REST clients all use IDOs to read and write data.

How can I list every IDO in my system?

Open the IDOs form in the development tools of your system and filter by name. You can also query the IDO metadata through the same request service if you have rights to do so.

Do IDO names stay the same across versions?

Core names are stable across many releases, but properties and methods change, and customers add their own IDOs. Re-test integrations after every upgrade and keep a list of the IDOs you depend on.

Can I add my own IDO?

Yes, custom IDOs can be defined over standard or custom tables through the framework. Follow the supported extension approach for your release so that upgrades carry them forward.

If you are building integrations against SyteLine, Netray can review IDO usage and draft documented, read-only access patterns that fit your security model.

Talk to an Expert Explore More Free Tools

Related Tools

Infor SyteLine

More Infor SyteLine tools

See all

Back to All Tools