Acumatica OData Extraction Issues / Trouble
Acumatica OData troubleshooting, hints & how-to’s. How to deal with warning messages and how to troubleshoot issues.
Related OData Troubleshooting Pages
- OData URL from an Acumatica Instance
How to put together a OData URL from an Acumatica instance. How to find the core Acumatica URL.
- Odata[0100.873]: The remote server returned an error: (403) Forbidden
Error Message: Odata[0100.873] - The contents of table <table-name> are not available for this user. The remote server returned an error: (403) Forbidden.
- ETL+ Troubleshooting for OData
Links to coverage of OData error messages, troubleshooting and solutions.
- OData Refresh Failure at Certain Times
Overnight refreshes from OData are failing at a certain time of day.
- OData: Message OData[0100] "contents ... not available"
ETL+ error message “OData[0100] - The contents of table xyz are not available for this use. The remote server returned an error (403) Forbidden.”
- How to Verify that OData v4 is Working
How to quickly verify that OData is running and working correctly.
- Row Counts Don't Match
Row counts in Acumatica don’t match number of rows extracted by ETL+.
- Failure to Load Tables
- GI Extractions Stop Working
Changes to Acumatica underlying DAC level and GIs can break ETL pre-mapped GI extractions.
Related Pages
ETL+ Design Page Key+ designation helps with extracting large tables from OData.