Skip to content
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

[BUG] 0.7.0 PO Import tools issues #3098

Closed
eeintech opened this issue May 30, 2022 · 5 comments
Closed

[BUG] 0.7.0 PO Import tools issues #3098

eeintech opened this issue May 30, 2022 · 5 comments
Labels
bug Identifies a bug which needs to be addressed import / export Data importing, exporting and processing wontfix No work will be done against this issue or PR
Milestone

Comments

@eeintech
Copy link
Contributor

Describe the bug

There are multiple issues with the Purchase Order import tool:

  1. When user selects a file, file name is shown twice

image

  1. On step 2, the file column names are missing from the view

image

  1. Still on step 2, the two actions buttons are "Previous Step" and "Upload File", but file was already uploaded

image

  1. Attempt to go to step 3 clicking on "Upload File" results in automatic error

image

Steps to Reproduce

Steps to reproduce the behavior:

  1. Click on an existing and pending purchase order
  2. Click on "Upload File" button
  3. Follow the form

Version Information
InvenTree-Version: 0.7.0
Django Version: 3.2.13
Commit Hash: 044315a
Commit Date: 2022-05-24
Database: postgresql
Debug-Mode: False
Deployed using Docker: False

Deployment Method: Bare Metal

@eeintech eeintech added the bug Identifies a bug which needs to be addressed label May 30, 2022
@matmair matmair added the import / export Data importing, exporting and processing label May 30, 2022
@matmair matmair added this to the 0.7.1 milestone May 30, 2022
@SchrodingersGat
Copy link
Member

I think we should make the leap and migrate the Purchase Order importer to the API importer (as is used for BOM importing)

Ref: #3097

@SchrodingersGat
Copy link
Member

There is too much work required here to fix this, as we will be overhauling the entire import tool in #3101

@SchrodingersGat SchrodingersGat added the wontfix No work will be done against this issue or PR label Jun 2, 2022
@matmair matmair mentioned this issue Jul 4, 2022
2 tasks
@Geekly
Copy link

Geekly commented Feb 28, 2023

Is there a workaround for this, or is importing for a PO just not going to work?

@eeintech
Copy link
Contributor Author

@matmair Could there be a workaround before 1.0.0 / #3101 gets around?

@matmair
Copy link
Member

matmair commented Feb 28, 2023

For sure; one could simply add the importer improvements discussed in the issue and close it. 1.0 is basically a big wishlist that signals that the issue would be nice and a lot of work.
I have in the back of my mind that @SchrodingersGat wanted to tackle it this year but I could be wrong about that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Identifies a bug which needs to be addressed import / export Data importing, exporting and processing wontfix No work will be done against this issue or PR
Projects
None yet
Development

No branches or pull requests

4 participants