We’ve been uploading price lists via FBDI without issues for months, but after the quarterly patch last week our bulk pricing uploads are completely halted. The FBDI file validation now fails with ‘Invalid file format detected in PriceList.csv at line 1’ even though we’re using the exact same template that worked before.
Our CSV file has standard columns: PriceListName, CurrencyCode, ItemNumber, ListPrice, StartDate, EndDate. File encoding is UTF-8 which has always been our standard. We’ve tried re-downloading the template from the documentation but the structure looks identical.
PriceListName,CurrencyCode,ItemNumber,ListPrice
STD_PRICE_2025,USD,ITEM-001,299.99
STD_PRICE_2025,USD,ITEM-002,450.00
Has anyone experienced FBDI template compatibility issues after quarterly updates? We need to upload 5,000+ price changes and this is blocking our entire pricing team.
Thanks for the suggestions. I checked the encoding and it was UTF-8 with BOM. Removed the BOM but still getting the same error. I also compared our template against the documentation and can’t spot any structural differences. Is there a way to get more detailed error logs from the FBDI validation process? The generic ‘Invalid file format’ message isn’t giving us much to work with.
The FBDI validation logs are in the scheduled process details. Go to Scheduled Processes, find your failed import, and download the log file. It should show which specific field or row is causing the validation failure. In my experience with quarterly patches, sometimes they add hidden validation rules that aren’t documented in the template guide. The log file will be more specific than the generic error message you’re seeing in the UI.
Found the detailed log - it’s complaining about missing ‘PriceListId’ column which was never required before. The quarterly patch documentation didn’t mention this as a breaking change. Do I need to populate this field for new price lists or can it be left blank?