Olivier Gagnon NC Red Ribbon

Why do you want a delay, where does this come in?

Did you add a debug log to see what was in custcol_ltr_ite_cube_feet? And how is it sourced? Is it store value false?

EDI is not e-commerce. E-commerce would imply the NS web store functionality, either Sitebuilder or SCA, which is a totally different debug path. In any case, add a debug log in your code and check out the value of custcol_ltr_ite_cube_feet How is this field supposed to be set? I am pretty sure SPS isn't setting it, so…

Yes I have done this in the past. You can manage your own mechanism using an HTML construct (instead of NS sublist) and then maybe something like a JSON cache to manage pagination. Worked well when I did it.

Try columns[0] = columns[0].setSort() although in theory that should not make a difference. If you comment out the line with the setSort, does the search execute properly? What kind of search is this, can you show the rest of the code up to the search call?

Is this for Suitescript 1.0 or 2.0? And do you mean that your script FILE was modified, or the script record in NS was modified and a function written into the postSourcing trigger? I would assume the latter - if so, what was the name of the function inserted? Did you check History/System Notes to see if anything was…

After Submit is not longer truly after submit. NetSuite made some changes (likely to optimize performance while sacrificing correctness). So you often have the case of values being returned incorrectly in after submit scripts when doing local getFieldValue type calls (both in SS1.0 and 2.0). The solution is typically to…

Ah. Can't be done, as far as I know. You would need scripting or maybe a workflow.

So your custom field would contain many values? What type of custom field is it?

@david.smith: I'm not sure I understand what you're asking. The exchange rate is taken when a transaction saves and then does not change by itself. @chris: I noticed amountremainingfx too, but this is new. Up until now, you wanted anything other than amountfx, you calculated it by taking the "regular" field and multiply by…

You can just multiply Amount or Amount Remaining by the Exchange Rate.

You are on a Suitelet. There are no local field value because there is no local record. nlapiGet anything will not work.Looking at this code, I believe you mean to say var customerId = recSO.getFieldValue('entity')

Ha, I literally coded this script about 5-6 years ago! Brings back memories... Anyway, yeah, NS will try to invoice everything fulfilled by default. If you want an Item Fulfillment-Invoice pairing, you'll need to be more surgical in your approach. You'll need to call a search to find newly created Fulfillments, and store…

You can code as many actions to occur as you want into custom buttons

Hi Greg, If you create a UI transaction saved search, on the results tab, you can set the "Consolidated Exchange Rate" field to "None". This will stop figures from converting to top subsidiary. You can then call this UI search in your code (rather than building a search directly from code).

Yeah there are countless pages where you can't deploy scripting. This will only work on records that support scripting. It won't be possible on anything that isn't a record (such as any listing) and any record type that doesn't support scripting. I would advise you add a Center Tab that leads to the (I presume) HTML…

I'm not sure I totally understand. Every time NS reloads ANY page? No, that isn't possible, and what you are doing is almost certainly very detrimental to system performance. What the heck is the business case anyway? Why do you need to do this?

Well if you use the standard Department and Location fields you can use the Role to default them on transactions. That would be much simpler.

Yeah I agree with khultquist, that's the only workaround I see. You'll need to have a schedule script edit/save all your records. It's a really, really bad workaround, but if that's all you got to work with, it'll do. You may need to recode some of your script though, for example if you have logic that needs to run on…

You can also try contacting NS Support. They have a whole Performance division that can help you figure things out.

Excellent, glad that solved it :)

Is each individual line of the receipt pinging the suitelet/restlet? You are probably hitting the script execution limit on the Item Receipt, not from the Suitelet.

10 seconds per entry seems rather long. Do you have scripts or workflows running against time entries? Do you have a bunch of custom fields on them? That can all significantly affect performance.

You need to execute the nlapiSubmitRecord from either a Scheduled Script or a Suitelet/Restlet. User Event and client scripts do not trigger scripting on the target record when they submit.

nlapiSubmitRecord returns the internal Id of the submitted record

Do you mean if(type!='delete')? If so, check the Help and see about the 'type' entry parameter.

Good God don't do that!

Follow up on this: when first testing I did a very basic error. In re-testing I can confirm that the After Submit event triggers on the creation of Drop Ship POs, as it should. Before Submit and Before Load do not, however. If I recall correctly, it has always been like that. Thus, while it is normally best practice to set…

Awesome, that's what I like to hear :)

Until very recently the creation of Drop Ship POs used to trigger scripting. In fact, there is even a trigger type for it under the 2.0 context. So looks like Netsuite recently broke the trigger. I'll be filing a case in regards to this.