3951833 Green Ribbon

Bump...Anyone know if scriptable cart works with SuiteCommerce Advanced and the SuiteCommerce API? From testing it seems like it is only available for the basic site builder. My expectation is that triggering the Add Item SuiteCommerce API would fire a validate line client event. Can someone confirm if this is the case?

I tested the scriptable cart using the basic site builder and I can get client events to fire. When using SuiteCommerce Advanced and the SuiteCommerce API in my files it doesn't trigger the client event... What is scriptable cart linked to? My understanding is that if I call the additem suitecommerce API, it should trigger…

Also, one other thing. Suitelets call user event scripts. Make sure this is intended.

Hi Darren. You are limited to 40 concurrent suitelet/restlet calls per account (which means executes and running at the same time). More than that you will kick out other suitelets that are running in the account. (I think NetSuite's documentations says 50 so you can go with that number).

What you've said is doable via script. I've implemented a solution in the past that does exactly what you mention. It sorts available lots by expiration and picks the oldest lots first and works it's way down.

One thought is that your body field is of field type text. You can try to parsefloat you values to convert to numerical and then retry.

Not sure its a typo but you have a space in your: nlapiTransformRecord('salesorder',soid,'itemfulfil lment') You can also try putting logs to read the internalid to see if the record generated or wrapping your code n a try/catch and read the error object. Also, make sure your using nlapiSubmitRecord with each of your…

Yes, you usually run into sourcing issues when setting fields in the before load even. Page init is the way to go for these sourced fields. Be careful that you are not setting too much fields in the page init (10+fields) or you may run into performance issues.

That worked great, thanks. I was hoping for speed purposes to not have to load the record, but this works for now. Instead of load you can try nlapiLookupField in view mode. It may be faster...

Thanks everyone for the suggestions. It may be more prudent to go with a scheduled script, although I am disappointed as I was hoping for a solution that synchs in real-time. My customer has SuiteCloud Plus which I think allows for simultaneous scheduled scripts to run at the same time, which my help to minimize how long…

Thanks Delainey. Your post is helpful. This made me think of a couple of questions: 1- If I call a suitelet from a user event script, does the time governance on the user event continue to run until the suitelet has finished executing? 2- Is there any difference between using: nlapiSetRedirectURL(type, identifier, id,…

Actually I'm trying to get this to work in real time so trying to avoid scheduled scripts. Chaining may be a confusing term. I'm working on a process to synch multiple records. I think I will do some more tests. If I need some more help I will reply here. Thanks for your help.

Just to circle back on this topic, as a test, I edited multiple records from a direct list edit to test if the submits to the database would submit synchronously or asynchronously. From my testing they submitted synchronously, which means that if I had a suitelet called in a userevent script, at any one time only one…

Thanks Olivier for your great feedback. I didn't realize you were limited to 40 concurrent suitelets. Normally I run tests to get answers but in the process its a little hard without spending a large amount fo time executing these tests. When a user executes on records, is the execution synchronous? Suppose I have a…

I setup something similar to this awhile ago. You can do this using scripted fields.

Hi Chris, In a before load script I added a field using the addField method of the form object. I then filtered the select values based on another field using the addSelectOption method of the field object. You can find these methods in the SS guide.…

You could also consider adding a button in a beforeload script and call a function that way.

I would suggest checking if any of your conditions are being triggered. Consider adding logs in each condition to see if this is the case (using nlapiLogExecution).

For option #1 you may also need to consider timeout limitations as I believe you may be limited by execution time limit.

I know someone was able to add a field to the item sublist on a sales order via script. I'm not sure what the exact configuration was but I think he used standard NS API. Maybe try the getSublist first and then add it to that object.

Yes native JSON support was a pleasant surprise.

Hi Feeney. Can you paste the URL that is generated in the online form when u actually click a link that has been sent out from a customer record? I believe parameters need to be set in the URL to update the relevant customer record. If that is already configured, its possible one of the tags are failing.

I'd like some more info on those parameters. Smitha can you use an execution context filter as a workaround?

Brett, that's cool. I don't see this documented in the help guide anywhere. Are there any more of these types of parameters that exist.

Does this work for on create as well?

I think this is what you mean Olivier but just to be clear. If we use those indexed fields vs. non-indexed fields in our search filters we will get the data faster? Does it matter what fields are included in the columns? Thanks.

Try to run the search via a test. Quotas are available as a UI search so would be surprising if you couldn't access via script.

That's frustrating. I have seen something like this in the UI, where someone had a different date format then other users. You can try 2 things: 1-check the users personal NetSuite preferences 2-validate the date format first

Olivier is right, no solution is perfect. A timestamp is the way to go to minimize the impact on other users. Personally, I don't like the beforesubmit approach as I think this would give a bad user experience. The user will not know there is a problem until they saved the record, which could mean a lot of wasted time…

I agree with JMU. I did run a test and saw that the script fired first but this is not reliable enough for me. What does NetSuite say about it? Also does this mean that if I wanted to fire the workflow before my script that this would not be doable?