-
-
Notifications
You must be signed in to change notification settings - Fork 402
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Import inventory results in incorrect binLocation !=null exception. #1633
Comments
Thanks for the bug report, @glenheiberg. Here's a summary of what I think the issue is, but I need to investigate to confirm. If I remember correctly, the inventory import assumes that all bin locations have been created already. Therefore, it's just just going to look up to see if a bin location exists and throws the exception if a bin was specified but does not exists. Admittedly, this should be made more clear by the error message and import instructions. FWIW, this is there to protect you from creating multiple bin locations based on typos (AB-CD-12, AB-CD--12, AB CD 12). We can look into changing the behavior to create a new bin location based on a config property if that's desired. |
So yeah that's what is happening in the import code
|
So the proposed solution would be to add all of your bin locations before doing the inventory import. If you only have a few you can use the first option under instruction 5. If you have a lot I would recommend using the second option.
|
Thanks Justin! I've created the Bin Locations, and it now imports correctly. |
version 0.8.11
Import inventory fails with assert binLocation != null | | null false
Select products, import inventory, download "Inventory template", fill out accordingly or leave example template, save.
Select data file. Enter date; click Upload.
Preview looks good. In particular the binLocation field shows the correct data. Click Finish.
Exception generated:
The text was updated successfully, but these errors were encountered: