Hi all, i am trying to CSV import some assembly it...
# general
n
Hi all, i am trying to CSV import some assembly items. I am getting an error on some lines that is very helpfully ""An unexpected error has occurred" Some items are already in the system but it wont let me update, some are not in and wont let me import. can create through the UI. I found this on suiteanswers but it was not this issue https://suiteanswers.custhelp.com/app/answers/detail/a_id/26803/loc/en_US I cannot see anything such as character issues etc. causing issue sin the data. There is no existing items with the same external ID (already checked that) Has anyone else experience this for Assembly Item Imports
j
Are scripts running?
n
Nope - turned those off.
and there are other assembly records loading with no issues. I am guessing there is an issue in one field in the clients data, but i cannot work out which one. in Sheer frustration before i unmapped everything that wasn't absolutely necessary to create an item and its working, but i am going to have to go back and troubleshoot what field is the issue.
j
weird. You might have to reach out to NS Support for this one, as it’s almost impossible to know where an Unexpected Error comes from unless you can actually identify which script and where in that script. If it’s in a NS native script you’re kinda on your own. For the ones that don’t load, what happens if you try to create them through the UI instead? Sorry I don’t use Assembly Items at my company so I’m not familiar with anything specific to those.
n
They create through UI no issues. i can at least get them loaded if i unmap alot of fields i will come back and grab a test item and then map in one field i took off at a time and see if i can isolate the issue that way. So bloody frustrating.
j
ugh, sounds super tedious
n
yep and i think its a different issue on the update from create lol - in 10 years i have never seen this on a CSV so i guess i have gotten lucky lol
This ended up being the Replenishment Method field and the Planning Item Category field - both fields appear to throw a generic error.