Good day.
I am trying to import item vendor lead times into the stock item profile.
See the attached. I keep getting the below error; the one that worked was blank.
Any suggestion/modifications need to the import scenario.
Thank you.
Solved
Item vendor Lead Time Import "Purchase Unit" Error
Best answer by riglesias
Hello
Sorry for the delay.
I restored your scenario in my demo and here are my thoughts.
I noticed the custom keys were setup by entering the field’s name between parenthesis which is incorrect. Also Line Number line is still active.
In this webinar, there is an example on how to setup custom key fields:
To setup a custom key using the @@ notation, you need to type the data field’s fields name which you can find by inspecting element. See example below where I inspected element for Vendor ID field:
Once you know the data field names for the fields you want to setup as custom key, you have to map this fields first, then the fields with the values you need the system to search by and at the end, the values that you need to be updated.
Please find below the screenshot of the corrected scenario mapping so you can use as reference:
Hope this helps.
If you still run into any issues, I would recommend you to create a case so I can review your instance and see what could be missing.
Have a nice day!
+13
Acumatica Functional Consultant & Customer Experience Supervisor
1 person likes this
+2Hello
If the vendor already exists under Vendors tab, when you map <Line Number> line to =-1 The system will try to add a new line instead of updating the existing Vendor with the corresponding time.
In this case I would recommend you to setup a custom key by using the @@ notation for Vendor ID field to update the line.
Here’s a link that explains how to setup a custom key to update existing lines on a grid (Min 44:56):
Rodrigo ~ A member helped you, please *Like* their post. A member provided an answer to your question, please mark it as *Best Answer*.
1 person likes this
+2Hello
Here’s how you need to map the import scenario.
- Deactivate <Line Number> line.
- Insert a line for the custom key (@@InventoryID)
Hope this helps.
Thank you for your response. I made the adjustment adding the @@ field. Same error? Is it in the wrong place? Or should it be custom field for vendors?
See screenshot.
I think
Basically, the “@@” tells the import to use the specified field to find a line which matches the field being brought in by the data.
In this case, @@VendorID will tell the import to use the VendorID field to find the line where the VendorID matches the value being brought in on the import scenario.
1 person likes this
+13manikantad18 wrote:
have you tried this Option?
Thanks
Acumatica Functional Consultant & Customer Experience Supervisor
1 person likes this
Thank you for your assistance. Please see the attached xml. I am still getting Purchase Unit issue. I then had an issue with Location but added the @@ field. I am not sure why this little scenario is such a problem. It basically a test; i am going to update all my items shortly.
+2Hello
Could you please provide a screenshot of Stock items screen for the item TB-94-M-3-2BES showing vendors tab?
Thanks!
Rodrigo ~ A member helped you, please *Like* their post. A member provided an answer to your question, please mark it as *Best Answer*.
1 person likes this
+2Hello
Sorry for the delay.
I restored your scenario in my demo and here are my thoughts.
I noticed the custom keys were setup by entering the field’s name between parenthesis which is incorrect. Also Line Number line is still active.
In this webinar, there is an example on how to setup custom key fields:
To setup a custom key using the @@ notation, you need to type the data field’s fields name which you can find by inspecting element. See example below where I inspected element for Vendor ID field:
Once you know the data field names for the fields you want to setup as custom key, you have to map this fields first, then the fields with the values you need the system to search by and at the end, the values that you need to be updated.
Please find below the screenshot of the corrected scenario mapping so you can use as reference:
Hope this helps.
If you still run into any issues, I would recommend you to create a case so I can review your instance and see what could be missing.
Have a nice day!
Rodrigo ~ A member helped you, please *Like* their post. A member provided an answer to your question, please mark it as *Best Answer*.
1 person likes this
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.