Infor SyteLine3 min readNetray Engineering Team

How to Set Up SyteLine ION Integration

Infor ION serves as the middleware backbone connecting SyteLine CloudSuite Industrial to other Infor and third-party applications. Proper ION integration enables real-time document exchange through Business Object Documents (BODs), event-driven workflows, and centralized data orchestration. This guide walks through the complete setup process from connection point configuration to BOD mapping and monitoring.

Configuring ION Connection Points

Navigate to Infor ION Desk > Connect > Connection Points to create a new SyteLine connection point. Select the Application type and specify the SyteLine logical ID, typically in the format lid://infor.syteline.1. Configure the ION API Gateway URL and authentication credentials. The connection point establishes the communication channel between SyteLine's IDO layer and the ION message bus, enabling bidirectional BOD flow through the IonServiceConfig table.

  • Set logical ID format as lid://infor.syteline.[instance] matching your tenant configuration
  • Configure OAuth 2.0 credentials from Infor Ming.le Security Roles for API gateway authentication
  • Map document flow endpoints to SyteLine IDO request handlers in ION Desk > Connect > Data Flows
  • Enable ION API file-based or real-time transport depending on your integration latency requirements

Mapping Business Object Documents (BODs)

BODs are the standardized XML documents ION uses to exchange data between applications. In SyteLine, navigate to Application Configuration > ION BOD Mapping to define inbound and outbound document types. Common BODs include Sync.SalesOrder, Process.PurchaseOrder, and Sync.ItemMaster. Each BOD maps to specific SyteLine IDOs such as SLSalesOrders, SLPurchaseOrders, and SLItems. Configure transformation rules in ION Desk > Connect > Mappings when field-level translation is required between source and target schemas.

  • Register outbound BODs under ION Desk > Connect > Document Flows with SyteLine as the source application
  • Configure inbound BOD processing rules in SyteLine's ION Event Processor background task (SLIonEvents)
  • Use ION Desk > Mappings > Field Mapping for transforming data types between SyteLine and target applications
  • Test BOD generation by triggering a sample transaction and monitoring output in ION Desk > Connect > OneView

Monitoring and Troubleshooting ION Flows

After configuration, validate the integration using ION Desk > Connect > OneView to monitor real-time document flow status. Failed BODs appear with error codes that reference specific IDO processing failures or schema validation issues. Check the SyteLine Event Manager form for queued ION events and their processing status. The IonRequestLog table in the SyteLine database stores all inbound and outbound ION transactions with timestamps, enabling detailed troubleshooting of data synchronization issues.

  • Monitor ION OneView dashboard for failed, pending, or reprocessed BOD transactions across all connection points
  • Check SyteLine background task SLIonBODProcessor for stuck or errored inbound document processing queues
  • Review IonRequestLog table entries filtered by CreatedDate and Status columns for transaction-level debugging
  • Enable ION API verbose logging in Infor OS Portal > ION API > Configuration for detailed HTTP request tracing

Frequently Asked Questions

How long does a typical SyteLine ION integration setup take?

A standard ION integration setup takes 2-4 weeks depending on complexity. Simple single-BOD integrations with one connection point can be completed in 3-5 days. Multi-application scenarios involving 10+ BOD types, custom mappings, and workflow triggers typically require 4-6 weeks including testing and validation cycles.

Can SyteLine ION integration work with non-Infor applications?

Yes, ION supports integration with non-Infor applications through the ION API Gateway and custom connection points. You can configure REST or SOAP-based endpoints as external connection points. The ION API Gateway supports up to 500 concurrent connections and handles authentication, rate limiting, and message transformation for third-party systems.

What SyteLine version is required for ION integration?

ION integration is fully supported starting with SyteLine version 10.1 and later. CloudSuite Industrial (CSI) versions 10.x include native ION connectivity. Earlier versions like SyteLine 9.x require the ION Connector add-on module. The recommended minimum is CSI 10.2+ for full BOD support with over 45 standard document types available.

Key Takeaways

  • 1Configuring ION Connection Points: Navigate to Infor ION Desk > Connect > Connection Points to create a new SyteLine connection point. Select the Application type and specify the SyteLine logical ID, typically in the format lid://infor.syteline.1.
  • 2Mapping Business Object Documents (BODs): BODs are the standardized XML documents ION uses to exchange data between applications. In SyteLine, navigate to Application Configuration > ION BOD Mapping to define inbound and outbound document types.
  • 3Monitoring and Troubleshooting ION Flows: After configuration, validate the integration using ION Desk > Connect > OneView to monitor real-time document flow status. Failed BODs appear with error codes that reference specific IDO processing failures or schema validation issues.

Need expert help configuring SyteLine ION integration for your enterprise? Contact Netray for specialized CloudSuite Industrial consulting.