I'll have to remember that one, I'm sure I'll run into it many more times in the future. Thanks Wee Ming.

No change I'm afiraid. It's deployed to all records as there isn't an option for location as a record to deploy to. But I can tell that it functions on the location record, as it does correctly prevent me from saving the record and displays the logs on the script record. Just that the message doesn't appear on the new…

That doesn't seem to be it, sorry. Although a good suggestion, it appears to be working without that change. However, it's working on most other forms and not the new location form. So it appears to be an issue with the page/form rather than the Script. Perhaps I should log this with support as an error? Here's an example…

A suitable fix. Thanks @Wee Ming ~!

I think I have it. By adding &xml=t to the url I was able to inspect the item receipt further and found the following fields in existence. One of these likely works, more than likely the amount one.

Ah ok, so it will fix itself at the next quarter. Though I am still curious if you know what might have caused this to begin with?

One of my users just got this notification emailed to them. This is me looking at the script in question that it warned them on the error. I'm not sure what caused it to trigger, 12 min after I ran the script you suggested that fixed my issue at 4:17. Should I be concerned?

This solved the original issue, thanks! Where did you find the answer and what is it that the script actually does? Based on the execution log it 'migrates assets with new and depreciating status' to the depreciation schedule? I don't know what that means if that's what it's doing.

OK, no I don't know if this Retrieve Asset Vales script works. It's throwing the same error on all of my other assets that have been generated normally and don't have the transfer location issue. Here's FAM000736 as an example. No issue transferring.

Oh, actually it didn't succeed. It completed, but there was a map error(?). map error FAM000750 {"type":"error.SuiteScriptError","name":"INVALID_ASSET_ID_FORMAT","message":"The specified Asset ID either does not exist or has an invalid format.","id":null,"stack":["Error"," at Object.create (/SuiteBundles/Bundle…

Attempted that just as you suggested it, haha. No success I'm afraid. I don't think the error has changed at all. {"type":"error.SuiteScriptError","name":"SSS_MISSING_REQD_ARGUMENT","message":"load: Missing a required argument: id","id":null,"stack":["Error"," at Object.getLoadParams…

At this point, I'm fairly certain it's the last purchase price.

Thought as much. Thanks for confirming.

Do I do an unbuild order and then a build order? Do I have to mark all of the components coming out of it and then all of the components going back into it? Seems a little tedious.

Sorry @Angela Bayliss, I'm not using Intercompany Cross-Subsidiary Fulfillment and I'm not asking new questions related to the initial post. I'm just answering JKLFU who has hijacked this thread, haha. I do intercompany transactions where our subsidiaries sell equipment to each other, not to customers. So we create a…

I should have clarified, I meant non inventory as in anything that is not inventory. Meaning that non-inventory, description, discount, kit/package, markup, other charge, payment and service, all of these item types cannot be used when creating an intercompany PO and further will not work in the manage intercompany sales…

An intercompany order cannot be created with non inventory items. You have to edit those in after you create and pair the orders.

Hey JKLFU, We put a customer tag on the bill from carrier company, and recharge the receiving subsidiary at the quarter end via billable expense. You could also consider creating a non-inventory item called Shipping Costs. You'd have to add this after the transaction have been paired though, as non-inventory items don't…

This proved as a fix for the following error I was having when user was attempting to update asset records via CSV: {"type":"error.SuiteScriptError","name":"INPUT_ERROR","message":"This role does not have permission to edit Asset record.","id":null,"stack":["Error"," at Object.create (/SuiteBundles/Bundle…

Sorry, must have been blind. I have the requestor join fields and they appear to be working for most records. Thanks!

Is requestor for you employee but labeled differently? As I don't have requestor join fields. I can get employee to work as a filter and employee… name as a column is working but only on certain record types like expense reports but not SOs, POs or Bills.

Looks good! Tysm~

Didn't work unfortunately. Issue seems to be that Number of Orders just doesn't have any value so when I did that I just got 1 line of 0. Perhaps it's on NetSuites end to check the functionality of this field.

I'll give it a whirl. Thank you both, for your insightful and helpful responses.

Ran into the same issue and this thread was the first search that comes up. I managed to make a scripting solution for it. It will update the To Location field correctly. The issue appears to be that NetSuite has labeled the fields wrong on implementation. Ideally, you should aim to fix the labels of these fields first but…

No, I need to get the text value so I'm going to have to create a second search. I think I need to move past this problem for now and revisit it later, as having the related purchase on my warranty record isn't necessary, I can just search for it manually with the serial number if need be. I'll likely revisit this after…

Sure thing, I've attached my script where I log out the value of inventorydetail.inventorynumber which comes out as the internal id of the serial number. Stored in the variable foundSerialNumber @Nicole Mendoza-Oracle has provided extensive breakdown of this already over in this thread where I first encountered the error…

I think what I may need to do is use the first search just for the customer and subsidiary, get the id of the inventory number record and run a second search on the inventory number record?

That all makes sense, but I think it's particular to my case as to why inventoryDetail.inventorynumber isn't suitable. What inventoryDetail.inventorynumber returns is a list of numbers which are the internal id's associated with the serial numbers in that list, not the actual text of that serial number. So it can be used…

Mm, I see.. tricky. Thank you for that, very insightful. I'll take another crack at it tmr.