Help Index → When something does not behave as expected → Use case 58
In Inventory Organizer, a full destination can leave whole item stacks in their original source. Review those leftovers before applying instead of assuming every routed category was moved.
Before you start
- Load and confirm the intended context; back up before applying. Before sync, formatting or structured refresh, copy EACH pending Raw JSON pane to its own external file: one sync can overwrite all others. Reapply non-inventory edits one pane at a time, syncing and comparing exact values before the next. Parse errors can leave an old tree with green status; [] is ignored, and Pretty Print can erase invalid text.
- Identify Organizer versus legacy Sorter. Their capacity behavior and result messages differ; do not interchange their instructions.
- Do not sync/Pretty Print Inventory Raw JSON: dictionary assignment is defective. Use Organizer for supported moves or Replace Items from Backup for supported replacement.
Steps
- Preserve EACH pending pane externally before refresh: one sync can overwrite the others. Reapply non-inventory edits one pane at a time, syncing and verifying exact values. Stop after parse errors even if green; [] is ignored and Pretty Print may erase invalid text. Use structured tools, never defective Inventory Raw JSON sync/Pretty Print. (control reference)
- In Organizer, click Review Moves and inspect visible source/category/destination counts. Post-review rows require a positive transfer to the assigned destination: retained-only or overflow-only rows may be omitted. Do not infer that no row means no leftovers. Use a before-operation context export to inspect actual source records externally without changing the reviewed candidate. (control reference)
- For a destination full result, check the chosen destination and your Optional settings. With expansion off, Organizer needs a free valid cell; it does not solve crowding by merging partial stacks or discarding an item. (control reference)
- If acceptable, choose a different destination, enable overflow to other Container storages, or enable expansion. Overflow tries eligible unassigned containers from Container 10 backward; it is not permission to use every inventory. Expansion deliberately changes capacity. (control reference)
- Generate a fresh Review Moves after changing choices. Inspect the visible proposal, but remember it may omit retained-only and overflow-only rows. Apply only if wanted; afterward inspect actual sources and all destinations for leftovers. Close instead to leave inventory data unchanged and reconsider the plan. (control reference)
Expected result
- Organizer retains an original source occurrence unchanged when no eligible destination cell is available. Moves use whole records, changing their slot Index as needed.
- A review may contain useful moves and leftovers together. Closing without Apply leaves inventory data unchanged, although choices can be remembered.
What changes, and when to save
Review is private; Apply changes app memory. Only a separately confirmed File → Save writes the loaded live target. Leftovers are not a reason to overwrite the disk save prematurely.
Check the result
- After Apply, compare source and destination item IDs, quantities and slot locations, including duplicate stacks. Check any overflow containers and expanded capacity, not just the primary destination.
Important details and recovery
- Enabling expansion can expand assigned destinations even when no item moves; inspect the proposal.
- If legacy Sorter reported a full target or validation warning, inspect actual contents. Its later Inventory has been sorted message does not prove that every requested move occurred.
- Legacy Sorter labels can shift when earlier inventories are missing. Prefer Organizer’s stable-path roster; compare actual inventory Name/Slots before any live save.