This site was built to compliment the existing NetSuite Professionals Slack Community by adding a means for members to easily find answers to common questions and to create a searchable database of those questions and answers.

NetSuite Professionals

Anyone know how to solve this? Trying to receive this active item and getting this error.

is it possible that you have two items with the same name, one active and one not?  If you global search for the item with the + sign added, do you get two results?

No, we do not have another with exact name. We have another with a similar SKU name, but it's active anyways.

I'm guessing a client script is running on the record

and there's an issue with that client script not pulling/querying correctly

if you go to Customization-&gt; Scripted Records and then look at the transaction type - look at the scripts deployed on it. (user event and client are the two that can generate an error like that)

I see no scripts running on this type of record: Inventory Item.

I do see 3  User Event Scripts on "Lot Numbered Inventory Item" though. Just our Celigo item mapping and File Drag and Drop scripts.

on the sales order/whatever transaction type you were doing

If i'm a betting man, have you all used lot numbered inventory items before?

NetSuite Platform Solutions Group - SuiteLabs File Drag and Drop
is the only script running on our transfer orders (where this error comes from)

We had to turn on lot numbered inventory items for WMS

Recently, a few weeks ago, WMS asked us to turn on Lot Tracking and Serialized Inventory, due to an issue with items not being able to be picked. This was their workaround.

Well, if you are sure there are no scripts running... then I suppose a call to NS support is in order.

Thanks though! I hate these one-offs. WMS has resulted in a lot of these quirky one-time bugs

maybe mark the item inactive, save it, and then unmark it inactive?

that was the first thing we tried unfortunately

Then it could very well be a defect with native behavior

and it *definitely* sounds like a call to NS

yup. I've uncovered several defects since the last update. I'll resolve with them.