Reading and Interpreting IDO Runtime Logs
log. xml file. Key error patterns to search for include 'IDORequestError', 'PropertyNotFound', and 'MethodInvocationException'.
Each log entry includes a timestamp, session ID, IDO name, method name, and full stack trace. Cross-reference the session ID with the user's SyteLine session to identify which form and action triggered the error.
- Locate IDO logs at C:\ProgramData\Infor\CSI\IDORuntime\Logs\IDORuntime.log on the utility server
- Set IDOTraceLevel to 3 in CSIServiceConfig.xml and restart the Infor IDO Runtime Service
- Search logs for 'IDORequestError', 'PropertyNotFound', and 'MethodInvocationException' patterns
- Cross-reference session IDs between IDO logs and active SyteLine user sessions for user-specific debugging
Resolving Common IDO Property and Method Errors
The most frequent IDO error is 'Property [PropertyName] not found in IDO [IDOName]', which occurs when a form references a property that does not exist in the IDO definition or underlying database view. Open IDO Metadata in SyteLine and verify the property exists under the correct IDO collection. COLUMNS WHERE TABLE_NAME = 'YourView' to confirm the column exists in the SQL view.
For method errors like 'Method [MethodName] not found', verify the method is registered in the IDO Methods tab and the assembly DLL is deployed to the IDO Extensions folder at C:\Program Files\Infor\CSI\IDOExtensions\.
- Verify missing properties in IDO Metadata form under the Properties tab for the target IDO collection
- Run INFORMATION_SCHEMA.COLUMNS query against the IDO's backing SQL view to confirm column existence
- Check IDO Methods tab for registered methods and confirm the assembly version matches deployed DLLs
- Deploy updated IDO extension assemblies to C:\Program Files\Infor\CSI\IDOExtensions\ and recycle the app pool
Debugging Custom IDO Extensions and Timeout Errors
Custom IDO extensions fail silently when assemblies have version mismatches or dependency conflicts. exe process hosting the IDO runtime to step through custom extension code. xml under the RequestTimeout element, the default is 300 seconds.
Long-running IDO operations like bulk updates should be converted to background tasks using the SyteLine Task Service. dm_exec_requests.
- Attach Visual Studio to w3wp.exe to debug custom IDO extension code with breakpoints and variable inspection
- Increase RequestTimeout in CSIServiceConfig.xml beyond the default 300 seconds for known long-running operations
- Check SQL blocking with SELECT * FROM sys.dm_exec_requests WHERE blocking_session_id <> 0
- Convert long-running IDO operations to background tasks via the SyteLine Task Service to avoid UI timeouts
Try it here, free
SyteLine IDO and SQL Performance Assessment
Score the performance risk of a SyteLine 9 or 10 on-prem install across data growth, IDO and extension code, background tasks and SQL Server configuration, with the specific fix for each weak answer.
Frequently asked questions
What causes 'IDO Extension Assembly Load Failure' in SyteLine?
This error occurs when the IDO runtime cannot load a custom DLL from the IDOExtensions folder. Common causes include .NET framework version mismatches, missing dependent assemblies, or file permission issues. Check the Windows Event Log for detailed fusion log entries. Ensure the DLL targets the same .NET version as the IDO runtime, typically .NET 4.7.2 or 4.8 for SyteLine 10.x.
How do I reset the IDO cache without restarting IIS?
Navigate to Utilities > IDO Cache Management in SyteLine and click Clear All Caches. Alternatively, recycle just the Infor CSI application pool in IIS Manager without a full IIS restart. This forces the IDO runtime to reload all IDO metadata from the database. Allow 30-60 seconds for cache rebuilding before testing the affected form.
Why do IDO errors only happen for specific users?
User-specific IDO errors typically stem from row-level security configurations, missing form permissions, or session-specific data states. Check the user's security group in User Permissions and verify they have access to the IDO collection. Also review FilterByUser properties on the IDO that apply user-specific WHERE clauses which may reference invalid data for that user.
Struggling with persistent IDO errors in SyteLine? Netray's integration engineers specialize in IDO diagnostics and custom extension development. Reach out for expert IDO troubleshooting support.