Overview
In TradeBeam iSupply, the i-Supply Receiving Manager History Export could generate an export where Snapshot values appear under the wrong column headers (notably Minimum and Loop Size). This was confirmed as a product defect caused by incorrect Snapshot export column ordering/mapping.
Engineering corrected the Snapshot export column ordering/mapping and deployed the fix to production (no version number was provided).
Solution
Symptoms
The exported file may show Snapshot values under incorrect headers due to a column ordering/mapping mismatch between:
- the on-screen Snapshot page, and
- the exported Snapshot section.
Reported symptom (verbatim):
- “Export functionality displays incorrect values in Minimum and Loop Size columns”
- “When exporting snapshot data, the column values are incorrectly mapped.”
Cause
A defect in the export logic caused the Snapshot columns in the exported file to be ordered/mapped incorrectly compared to the on-screen Snapshot section. As a result, correct underlying values appeared under the wrong headers (for example, under Minimum and Loop Size).
Fix
Engineering corrected the Snapshot export column ordering/mapping so the exported Snapshot section aligns with the on-screen Snapshot page. The fix has been deployed to production.
Tracking references: internal defect ticket <jira_ticket> and engineering maintenance issue <eng_issue>.
Customer action (post-deployment validation)
- Navigate to the iSupply area that provides the Receiving Manager History Export (Snapshot/history export).
- Re-run the export using the same scope/filters used previously.
- Open the newly generated export and confirm the Snapshot headers align with the values.
What to verify
In the exported Snapshot section, confirm these columns display the expected values (matching the on-screen Snapshot page):
Inventory LevelMinMaxLoop MinLoop Size
If the issue still appears after re-exporting
- Confirm you are using a newly generated export created after the production deployment (not an older downloaded file).
- Capture side-by-side evidence:
- A screenshot of the on-screen Snapshot section
- The corresponding rows/columns in the exported file
- Include the export time and relevant context identifiers using placeholders such as
<item_id>and<location_id>so the export output can be revalidated.
Frequently Asked Questions
- 1. How do I know I’m seeing the same issue?
- If the export shows Snapshot values under the wrong headers—especially
MinimumandLoop Size—and those values do not match what the on-screen Snapshot page displays, you are likely encountering the same column mapping/ordering defect. - 2. Is there an exact error message?
- No. There is no required system error string/code for this issue. The indicator is the symptom: “Export functionality displays incorrect values in Minimum and Loop Size columns” due to Snapshot columns being incorrectly mapped in the exported file.
- 3. What changed to fix it?
- The Snapshot export column ordering/mapping was corrected so the exported column layout matches the on-screen Snapshot page, preventing values from appearing under the wrong headers.
- 4. What should I do after the fix is deployed?
- Re-run the export and verify the Snapshot columns (
Inventory Level,Min,Max,Loop Min,Loop Size) now match the on-screen Snapshot page. - 5. What if the exported columns are still wrong after I rerun the export?
- Confirm the file is newly generated post-fix (not an older download). If it persists, provide a comparison of on-screen Snapshot vs. export output and include the export time and relevant context identifiers (for example,
<item_id>and<location_id>) so the behavior can be revalidated.
Priyanka Bhotika
Comments