How to Call SyteLine IDOs from an External Application
How to call SyteLine IDOs from outside SyteLine using web services
Also searched as
- syteline soap api integration
- idorequesthandler.asmx how to use
- call syteline ido from external application
- syteline web service integration c#
Short answer
SyteLine exposes its IDO layer as a SOAP web service, commonly published through an IDORequestHandler endpoint, so an external .NET application, middleware platform, or script can Load, Update, Delete, and Invoke methods on the same IDOs the SyteLine client itself uses. You call it like any SOAP service: reference the WSDL, authenticate, and pass the IDO name, method, and parameters in the request.
Applies to: SyteLine 8.x, 9.x, CloudSuite Industrial (CSI) 10.x on-prem SOAP integration; CSI cloud tenants commonly also use ION API/BODs for integration
Consume the IDO SOAP service from external code
- 1Confirm the IDO web service is enabled for your SyteLine instance and note its base URL, typically an IDORequestHandler endpoint published from the SyteLine application or web server.
- 2Add a service reference in Visual Studio from the WSDL, or, for non-.NET clients, build SOAP envelopes by hand against the published operations.
- 3Authenticate using the credential mechanism your environment expects for web service calls - a dedicated integration user account is strongly preferred over reusing an interactive user's login.
- 4Call Load to read a filtered set of rows from an IDO, passing a query or filter expression the same way the client would when opening a browse.
- 5Call Update, Insert, or Delete to write changes, and check the IDO-level error and result payload rather than assuming a successful SOAP response also means the business logic succeeded.
- 6For custom operations, call Invoke against a custom IDO method the same way you would a built-in one, passing the parameters defined on that method's Methods tab.
- 7Log the raw request and response payloads during development so you can see exactly which IDO validation or extension-class error came back when a call is rejected.
What the IDO web service actually is
The SOAP endpoint is a thin wrapper over the same IDO runtime the SyteLine client itself talks to, so anything reachable through a form - reading a filtered list of orders, updating a field, running a custom method - is also reachable programmatically through the same IDO calls made interactively.
This is why it has been the standard integration point for middleware - EDI translators, custom .NET utilities, older iPaaS connectors - for years, long before ION API existed as an alternative for cloud tenants.
Authentication and a dedicated integration account
Use a dedicated service account scoped to only the IDOs and operations the integration needs, both for audit clarity - you can tell integration traffic apart from a real user in logs - and so a credential change for a human user does not silently break an automated integration.
Some environments require the service account to hold an appropriate license or user seat, which surprises teams that assumed a service account would be free; confirm licensing before committing to the design.
Error handling - SOAP success is not IDO success
A SOAP call can return a valid, successful transport response while the IDO itself rejected the operation - a validation failure inside a BeforeUpdate extension hook, for example. Integration code must inspect the IDO result or error structure in the payload, not just the transport-level status, or failed writes will silently look like they succeeded.
SOAP versus ION API for CSI cloud
For CloudSuite Industrial tenants hosted by Infor, ION API and BOD-based integration is generally the sanctioned path for new cloud-to-cloud integrations, while the classic SOAP IDO service remains common for on-prem installs and for legacy integrations that predate ION.
Before building new integration work against SOAP on a CSI cloud tenant, check with Infor or your implementation partner on which path is currently supported and preferred for that scenario.
Common pitfalls
- !Treating a successful SOAP response as success without checking the IDO-level result payload for a business validation error.
- !Reusing an interactive user's login for the integration account, so a password reset or license reassignment silently breaks the integration.
- !Not handling IDO-level locking or concurrency errors - an integration that just fails hard on these instead of retrying can drop transactions.
- !Passing filter or query syntax that does not match what the target IDO expects, which usually returns an empty result set rather than a clear syntax error.
- !Building new integrations against the classic SOAP endpoint on a CSI cloud tenant without checking whether ION API/BOD is the currently required path.
- !Not logging raw request and response payloads during development, making an extension-class rejection far harder to diagnose after the fact.
How an ERP-grounded AI assistant handles this
SyteRay can generate the client-side integration code for a specific IDO call - the WSDL reference, the request shape, and the error-payload handling - from a description of what the integration needs to do, and can flag when a target IDO has an extension class or custom method that might reject the call under conditions not obvious from the IDO's field list alone. For teams already on ION API, it can also help decide which integration path fits a given cloud-to-cloud scenario.
Frequently asked questions
Do I need a SyteLine license to call the web service?
In most environments the integration or service account still needs an appropriate license or user seat, since it is consuming the same IDO runtime under the hood. Confirm licensing requirements for your specific environment before building the integration.
Can I use the SOAP IDO service from a non-.NET language?
Yes - since it is a standard WSDL-described SOAP service, any language or platform with SOAP client support, including Java, Python, or integration platforms like Boomi or BizTalk, can consume it, not just .NET.
Why does my Load call return zero rows when I know data exists?
Almost always a filter or query expression that does not match what that IDO expects, or a site and security context on the integration account that excludes the rows. Test the same filter interactively against the IDO first to confirm it returns the expected rows.
Is the SOAP IDO service still relevant on CloudSuite Industrial?
It is often still available for on-prem-style integrations, but Infor generally steers new CSI cloud integration work toward ION API and BODs. Check current guidance for your tenant before committing new development to the classic SOAP endpoint.
Related
How to Add a Custom Method to a SyteLine IDO in C#
Custom IDO methods let you expose new server-side business logic - beyond the standard Load, Update, and Delete - as a named, callable operation from the SyteLine client, a script, or an external integration. You declare the method and its parameters on the IDO Collection, then implement it in an extension class that handles invoke calls for that method name.
AdvancedHow to Add Custom Business Logic to a SyteLine IDO with an Extension Class
SyteLine lets you add validation, defaulting, and side-effect logic to any IDO without touching Infor's generated code, by writing an IDO extension class in C# and hooking into the object's Before/After events. The extension assembly is compiled, deployed next to the IDO Runtime, and picked up once the runtime cache is refreshed.
AdvancedHow to Build SQL Views for Custom SyteLine Reporting
Reports should read from purpose-built SQL views, not directly from SyteLine's core transactional tables, so an Infor patch cannot silently break them and heavy report queries do not lock rows the ERP itself needs. Put custom views in their own schema or under a clear naming convention, build them on stable base tables, and grant reporting tools read access to the views only.
Error fixDiagnose and fix a failed BOD document flow in ION Desk
A Document Flow showing Failed in ION Desk means a BOD (Business Object Document) stopped either at schema validation, at the mapping step, or at the target application. Open the failed instance's detail to see the exact failing element, fix the source data or mapping, then use Resubmit rather than re-triggering the original transaction to avoid duplicates.
Error fixFixing SyteLine's 'Object reference not set to an instance of an object' error
This is a generic .NET NullReferenceException surfacing through the SyteLine IDO Runtime, not a SyteLine-specific error code. It almost always means a form, script or IDO method referenced a field, row or object that came back null, usually after a customization, a missing related record, or a view/IDO method call before the form finished loading. Turn on detailed client logging and check the most recent customization or form event first.
Error fixDiagnosing and fixing SyteLine session timeout errors
SyteLine session timeouts come from one of three independent layers: the IDO Data Service session timeout on the app server, the IIS/application pool idle timeout for the web (Mongoose Web) client, or a load balancer/proxy idle timeout in front of a CloudSuite hosted environment. Fixing the wrong layer is the most common mistake - you need to identify which layer is actually expiring the session before changing anything.
AI for ERPAI Agents Over Infor ION API, BODs, and the Infor Data Lake
Build AI agents on Infor ION API Gateway, BODs, and Data Lake, alongside or instead of Infor's own GenAI features, with your choice of model and hosting.
AI for ERPAI for Infor SyteLine and CloudSuite Industrial
Add grounded AI to Infor SyteLine or CloudSuite Industrial: natural-language answers, agents over IDOs and ION, on-prem or CloudSuite deployment.
Stuck on Infor SyteLine (CloudSuite Industrial)?
Talk to engineers who work inside Infor SyteLine (CloudSuite Industrial) every week, and who build private AI that answers these questions from your own ERP data.