Import stuck on mapping columns

[jgreenemmw]

I've been tasked with seeing if InvenTree would be a good fit for our business. We don't have an IT department here. I don't know what I'm doing, really. I've set up the server using Docker desktop. I've been trying to import data from an .xlsx and a .csv version of the same file. I've started a part import session and mapped out the columns that were detected. When I save it just stays at "Mapping Columns" on the status screen. I tried making a separate Docker container for the worker as well and it still does the same thing. I tried the xlsx and csv with and without the separate worker container. I'm not sure what to do next to try to get it to work.

[westinpigott]

I had this same problem yesterday using new UI specifically with new Parts. I did not have the same problem with creating new Stock Locations using new UI. I was able to import the parts using the old UI (/admin/part/part/import/). Its not as clean or user friendly, but it does work.

[jgreenemmw]

thanks for the reply. I tried using this method and I'm just getting errors about the format being wrong with decimal conversion syntax errors. I saved it all as csv utf8 even though it gives the option to import as xlsx, which it originally was but it didn't like that at all. The parts we use have decimals in their exact names. I can't go through 4k+ inventory items to remove decimals and then replace them all after it imports, that is terrible. I guess I'm stuck until they fix the functionality on the new UI import ability.

[SchrodingersGat]

Hey guys please see this related issue - #9291

If you can provide some screenshots of the problem and a sample data file so I can recreate the issue, that would be very helpful

[jgreenemmw]

Thanks for the reply. The related issue you linked is similar but not quite the same. Here are some screenshots and some sample data. I first go to the admin data import panel and start a new data import session. After mapping all of the columns that are auto-detected from my xlsx on the left to the defaults on the right, I hit the big blue save button at the bottom. It then takes me original data import session screen and shows the session with the status of Mapping Columns and stays there even after 24 hours or more it never changes. I would appreciate any insight on how to remedy this.
First50xlsxGitHub.xlsx

[SchrodingersGat]

@jgreenemmw ok I see the issue here - the data import process is managed through the frontend user interface - not the django-admin panels.

As we are transitioning from the old UI to the new (react based) UI there are some discrepancies between the "stable" and "latest" versions of documentation.

Which user interface ("old" or "new") are you running?

• If you are on the old UI, refer to the stable docs
• If you are on the new UI, refer to the latest docs