Bulk price list upload fails in pricing management with CSV validation errors

ERP Infor CloudSuite
, , , , , , , ,
1

We’re experiencing consistent failures when attempting bulk price list uploads through the Pricing Management module. Our CSV files contain approximately 2,500 line items with tiered pricing structures across multiple customer segments.

The import process fails around row 800-900 with generic validation errors, but the error log doesn’t specify which rows or fields are problematic. We’ve verified our CSV template matches the standard format, including all required columns (SKU, Price, EffectiveDate, CustomerSegment). The concerning part is that partial data gets committed before the failure, creating inconsistent pricing in the system.

Has anyone dealt with row-level error logging in bulk imports? We need visibility into which specific rows fail validation and whether there’s a way to implement proper rollback for partial imports that don’t complete successfully.

2

The partial commit behavior is actually by design in the standard import framework. Each row is processed independently, so failures don’t roll back previous successful rows. You’ll need to implement pre-validation before submitting to the actual import API. Create a staging table, validate all rows first, then only submit if everything passes. This gives you control over the transaction boundary.

3

Thanks for the suggestion. We tried splitting into 500-row batches but still getting failures, though now they’re more random. The partial commit issue is really problematic because we end up with some prices updated and others not, which creates customer billing issues. Is there a configuration setting to enforce all-or-nothing imports?

4

I’ve seen similar issues with large CSV imports. The validation engine in ICS 2021 can be temperamental with batch sizes over 1000 rows. Try splitting your file into smaller chunks of 500-750 rows each. Also check if you have any special characters or currency symbols that might not be properly escaped in your CSV format.

5

For row-level error visibility, you need to enable detailed import logging in the CloudSuite admin console. Go to System Configuration > Import Settings and set LogLevel to ‘DEBUG’. This will generate a detailed error file showing exactly which rows failed and why. However, be aware this creates larger log files. For the rollback issue, the standard import doesn’t support transactions across the entire file, so implementing a two-phase validation approach as mentioned earlier is your best option.

6

Check your CSV encoding too. We had issues where UTF-8 with BOM was causing silent validation failures. The import would process but skip rows without logging why. Convert to UTF-8 without BOM and ensure line endings are CRLF not just LF. Also verify that your date formats exactly match the system locale settings - we’ve seen EffectiveDate parsing fail when using MM/DD/YYYY vs DD/MM/YYYY inconsistently across regions.

7

I’ll address all three critical aspects of your bulk import challenge:

CSV Template Requirements: Your template needs strict adherence to the ICS 2021 pricing schema. Beyond the standard columns, ensure you’re including: PriceListID (mandatory foreign key), CurrencyCode (ISO 4217 format), UnitOfMeasure, and MinimumQuantity for tiered pricing. The template must have NO trailing commas, consistent delimiter usage (comma vs semicolon based on locale), and proper text qualifiers for fields containing special characters.

SKU,PriceListID,Price,CurrencyCode,EffectiveDate,CustomerSegment
PROD-001,PL-2024-Q1,125.50,USD,2024-03-01,WHOLESALE
PROD-002,PL-2024-Q1,89.99,USD,2024-03-01,RETAIL

Row-Level Error Logging: Enable comprehensive logging through CloudSuite admin panel: System Configuration > Data Import > Advanced Settings. Set these parameters:


import.validation.mode=STRICT
import.error.detail.level=ROW
import.error.output.format=CSV

This generates a companion error file (filename_errors.csv) that maps each failed row to specific validation failures. The error file includes: RowNumber, FieldName, ErrorCode, ErrorMessage, and RejectedValue.

Rollback for Partial Imports: The native import API doesn’t support transactional rollback across the entire file. Implement this two-phase approach:

  1. Pre-validation Phase: Submit your CSV to the validation-only endpoint before actual import:

POST /api/v1/pricing/import/validate
Content-Type: text/csv

This returns all validation errors without committing any data.

  1. Conditional Import: Only proceed with actual import if validation returns zero errors:

if (validationResponse.errorCount == 0) {
  POST /api/v1/pricing/import/execute
}
  1. Backup Strategy: Before each import, export current pricing data as a rollback snapshot. If partial import occurs, you can restore from this backup.

For your specific 2,500-row scenario, I recommend batching at 250 rows per file with sequential naming (prices_batch_001.csv, prices_batch_002.csv, etc.). Process each batch through validation first, collect all error reports, fix issues across all batches, then execute imports sequentially. This approach gives you granular control and easier troubleshooting.

Alternatively, consider using the CloudSuite ION integration framework which provides built-in transaction management and automatic rollback capabilities for failed imports, though this requires additional configuration and BOD message mapping setup.