I know this thread is a month old but thought I would post some of my findings. I can confirm the inter-company transfer order can be created via web services. This is not even close to ideal. In my test I created a web page in .NET and hosted on a public facing server (not with NetSuite). I then had a suite script that…

I thought about this some more and I realized, Net Suite already offers the ability to store credit cards on the customer record and be PCI compliant. Given the rarity of needing to use multiple cards for one order, I think it can be sold as a business process that in order for our company to accept payment in this way we…

That would be awesome if you could do select statements. You can't use select statements and you can't target a specific field I don't think in the global search either. You can target record types. From a criteria perspective maybe look at it as your text in the global search is targeting every indexed field in your…

In afterSubmit of the project record, context.newRecord.id should have a value where as beforeSubmit it would not. Your understanding of oldrecord is correct, I would only add in new record creation oldrecord is null I believe.

If you're creating notes on a user event script of a project or something else it would have to be after submit. Until the new project record is saved to the database you wouldn't have an id from the project to use on the note record.

You would use record and recordtype if you were attaching to a custom record. If attaching to customer, vendor, employee you would use the entity field. If attaching to a transaction you would use the transaction field.

You can load a customlist record object with record.load or search for custom list with the search api, the search type would be ID of your custom list not the internal id. I believe things like Class, and Department are scriptable records (check the SuiteScript Records Browser) which means you could leverage the search…

There is no package column on an item fulfillment record is there? If you're wanting to target the package sublist on the record I don't think at present time this can be done as none of the package sublist is exposed via search. A work around would depend on when and why you want to search the package sublist. Load will…

AmyVNGI Where is the script from without the entire script hard me to know the script type. You mentioned SuiteAnswers do you have link to the page? Nevermind I found the SuiteAnswers page https://netsuite.custhelp.com/app/an...omer%20deposit This is just the shell of an example of how you could process the file it's not…

I think the error is your getValue. The summary option should be search.Summary.SUM <span style="text-decoration:underline">searchResults[i].getValue({ name: 'custrecord_allocationpercent', summary: search.Summary.SUM })</span>

anuscaria From the subsidiary field it appears no you can't use lookupFields. A custom multi-select field works so it's possible other native multiple select fields work and it's just the subsidiary that fails. So you have two options. 1. Load the item record which then you'll have access to all subsidiary values. 2. Run…

Looks like you might have found a bug. Your code looked fine to me, ran a test and I noticed the same thing on an item that had two Subsidiaries selected only the first in the selection is returned. Yet a multiple select custom field on the item returns all selected options. If the lookup field on the subsidiary column was…

I don't think you're missing anything. I went to a session at SuiteWorld this year about EcmaScript and how they might leverage the latest in EcmaScript in the future. There's a slide or two in the presentation about sublist access that might show where they might go but no promises. Here's the presentation on Suite…

On a reversal entry the createdfrom field on the reversal entry would be the source entry that originated the reversal. You could create a non-stored body field of type inline html and build the HTML link that way no script required. You would use a formula on the body field checking for not null and just build the HTML…

AmyVNGI With no script experience you have to be careful. What you're trying to do is creating a posting transaction in your General Ledger. If you don't have a sandbox account when the script runs and doesn't do exactly what you want then you have a bunch of customer deposits you have to potentially manually correct. Not…

There's nothing wrong with a script only solution :-) Perhaps a user event script on create of a journal entry that checks if the created from field is not null and if it isn't you can build the URL in script and save it on the record.

What error do you get? I would add some some logging to get a better idea of where it's failing. With what you've mentioned so far I would double check the easy things like data to make sure the customer column is an actual internal id of a customer record in NetSuite and the payment is numeric value. Depending on the…

The code looks wrong to me attributes options is not part of the to block according to the documentation shouldn't it be var id = record.attach({ record: { type: 'contact', id: obj[params.id] }, to: { type: params.type, id: params.id }, attributes: { role: -10 } });

j.j Focusing on the client side if you created a module level variable like entryPointCount in my example and instead called it currentRecord and and on pageInit did the following you would have a module level reference to current record that could be used anywhere within that module. // Get a module level reference to…

A 2.0 module isn't global but it doesn't sound like you need global a 2.0 Client Side Module can have module level variables that are shared across the different entry points in the same module. Just a simple example of what I mean define([]], function() { var entryPointCount = 0; function pageInit(scriptContext) {…

On a transaction search you have access to the Shipping Address record and could reference the phone.

Have you done an old fashion record load from the browser console on the client side and looked at the record. Looks like the price field could actually be price_1_ if you have tiered pricing you'd have price_2_ price_3_ for every tier that has a value.

michoel Thanks for the reply. That reminded me I've done something similar a long time ago. Perhaps I was just hoping I still didn't have to rely on a customization to download a file from the file cabinet.

One way is in your code you just have a hash matching the itemtype string to the record type string. var itemRecordTypeLookup = { "InvtPart":'inventoryitem", "Service":"serviceitem" }; log.debug('Item Record Type',itemRecordTypeLookup["InvtPart"]) // Would debug print inventoryitem Another approach would be lookupField…

While this on the surface is a definite annoyance and bottleneck as others have indicated. Could this not be overcome with a customization. At a really over simplified example could you build your own dropdown list of employees based on a search which could include inactive employees. Now that you have the id or name of…

The variable declaration var text does not need to be declared in the for loop. Perhaps you missed typing your example but I don't see you running your search. nlapiCreateSearch does not run the search it returns a search object. Olivier, is correct to point about running searches in a for loop. You would be better off…

I don't see Document or File in the Search.Type enum in the help. Try using the string 'file' apposed to search.Type.Document.

Are you just logging the n/file object? If so That's a JSON string representation of the object and not necessarily representing what properties are accessible on the object instance itself. type is not a member of the N/file object Perhaps you mean fileType?

You could add a new text field to your custom record that sources the sales description from the item field on your custom record. Or you could lookup the sales description on demand with search.lookupFields

The sales order needs to be successfully saved first but once it has, here's a SuiteScript 1.0 example var nte = new nlapiCreateRecord('note'); nte.setFieldValue('note','Some note'); nte.setFieldValue('transaction',salesOrderInternalId); nlapiSubmitRecord(nte) 2.0 way var nte = record.create({ type:'note', isDynamic: true…