InvenTree: V0.8.4 Missing parameters in BOM export CSV format
Please verify that this bug has NOT been raised before.
- I checked and didn’t find similar issue
Describe the bug*
When exporting a BOM, CSV and XLSX output files are different. In the CSV, parameters from the last component are missing (missing SKU and other empty parameters):
1,117,44,CSBRD22005,LINKY DEVELOPMENT BOARD,27,CS00026,DIGITAL_ISOLATOR_ADuM3402,QUAD-CHANNEL DIGITAL ISOLATORS,False,1.0,0,,U5,,0,0,,,,,+105,-40,SOIC16,,7.12€,,,,,,ANALOG DEVICES,ADUM3402BRWZ,MOUSER,584-ADUM3402BRWZ,,,,,,,,
1,118,44,CSBRD22005,LINKY DEVELOPMENT BOARD,40,CS00039,SINGLE_OPTO_DIGITAL_LTV-M601,High Speed 10MBit/s TTL Compatible Optocouplers,False,2.0,0,,"U6, U7",,0,0,,,,,+85,-40,SO4-5,,0.7€,,,,,,LITE-ON,LTV-M601,LCSC,C123201,MOUSER,859-LTV-M601,,,,,,
1,119,44,CSBRD22005,LINKY DEVELOPMENT BOARD,32,CS00031,QZ_12MHz_3.2x2.5_15ppm,Quartz CRYSTAL 12MHZ 8PF SMD,False,1.0,0,,Y1,,0,0,,,,12MHz,85,-40,3.2mmx2.5mm,,0.5€,,,,,,NDK,NX3225SA-12MHz-STD-CSR-6,LCSC,C481400,MOUSER
The save BOM as a XLSX file:

Steps to Reproduce
Export BOM as CSV and XLSX file. I don’t have any other BOM to test against another set of data.
Expected behavior
Both files must contain the same parameters
Deployment Method
- Docker
- Bare metal
Version Information
Version Information:
InvenTree-Version: 0.8.4 Django Version: 3.2.15 Commit Hash: ca1fbf9 Commit Date: 20/10/2022 Database: postgresql Debug-Mode: False Deployed using Docker: True
Relevant log output
No response
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 15 (11 by maintainers)
Commits related to this issue
- V0.8.4 Missing parameters in BOM export CSV format Fixes #3907 — committed to matmair/InvenTree by matmair a year ago
- V0.8.4 Missing parameters in BOM export CSV format (#4476) Fixes #3907 — committed to inventree/InvenTree by matmair a year ago
I’ll try to reproduce it or at least do some tests to check if it’s because of a special character.
This is a hard one, I tried with multiple versions and environments. Sometimes it reproduces - sometimes not. The crux is that it is not stable and I never get it to reproduce with debug=true.
@fjullien would you feel comfortable sharing a database dump through private channels so we can maybe try to reproduce that way? If yes please connect via code <AT> mjmair <DOT> COM
I would really love to get to the bottom of the problem rather then just ignore it.