My Stuff
Comments
-
I originally had that Lorne, but that was before I realized that datain was case sensative :) Thanks
-
I just ran into a similar issue - Check to make sure the script is not executing under a role with no permissions to the search. It's likely a permissions issue
-
Thanks for the reply Frederic, I appreciate the &xml=T trick, very helpful :) It's too bad that this sublist isn't properly supported, we have alot of logic surrounding locations, quantities etc and It'd be nice for some official support, but lets hope for 2013.1... Thanks again
-
Why not use an online form to do this? You can create a form for addition to your website that will create a custom record within NS that you can have your field managers access for lead data. To get more information on online forms access it via the help system: SuiteCloud ->SuiteBuilder->Custom Records -> Online Customer…
-
In our case we charge during transformation as we wont fulfill the order until the card is approved. I'm almost positive that the transformation itself is what triggers the card to be charged.
-
So it is, thanks Oliver!
-
Thanks for the reply Richi, We had considered doing a search for the item type as well but we wanted to keep our searches to a minimum. In our situation we can have a varying amount of items on our sales orders ( upwards of 30+ ). With each searchrecord call taking 10 units, I wanted to find a way to get the information…
-
We implemented this too, same process with the transform, only we run it from a saved search. What we do is transform the record, then load the cash sale and determine if the ccapproved box is checked or not , if its not checked the credit card failed to process, otherwise processing was fine. We flag a custom checkbox…
-
Thanks for the reply Mark, Hello, If you want to do programming things behind the scene, you can use nlapiLookupField on the Item Record. nlapiLookupField only operates on body fields from what the help center says. Have you used it on line items before?
-
I've always found that an unexpected error is a missing required field. Try recreating the same invoice that failed in the UI and see if you get an error, if so, what was missing? Also check the web service log for an error - it may be more helpful if the unexpected error is being triggered by a try/catch block and is not…
-
Thanks for the reply Oliver. I didn't think web services would fire due to the context, but was worth a shot. It seems that the changes will need to be made on the SuiteTalk side of things (where the regex can work in the proper context ) rather then on the server side. Thanks again, -Robert
-
Hi eschneids01, To solve this issue we have a script that rejects cash sales if the item is backordered. You may wish to try something like this in your code: function add_updateCashSale(datain){ var recordtype = datain.recordtype; var status = datain.status; var customform = parseInt(datain.customform); var createdfrom =…
-
I wrote a method in suitescript for this. It shouldn't be too hard to port it to Java or C#, requestedLocations can take an array of location ID's like this: var rLocations = ['1','20','19','3']; returnInvQty('mysku','rLocations'); or single location ID's like: returnInvQty('mysky','7'); Hope this points you in the right…
-
lol in lieu of a facepalm I'll use the wall :D :h_a_w:
-
Thanks for the reply Frederic, I figured it out :) Turns out that kit packages are the failure case. I resolved by passing the item name through a name parser that strips off our kit names and leaves just the main sku name, once I had the main sku I was able to pull inventory successfully.
-
Working code for any who may need it: var kit = nlapiLoadRecord('kititem',kitId); var lineCount = kit.getLineItemCount('member'); var itemId; var qty; var members = new Array(); for(i=1;i<=lineCount;i++){ nlapiSelectLineItem('member',i); itemId = kit.getLineItemText('member','item',i); qty =…
-
lol, Interestingly enough I have been unable to reproduce the issue since about 4:30 pm EST yesterday :confused: The javaException was happening in the NS Cloud as my app is developed using C# and suitescript. If it happens again I'll be sure to post.
-
Depending upon what you are trying to do with the fulfillment you may be able to work around the limitation with saved searches etc. Can you shed some light on what you are trying to accomplish?
-
As far as I know, all system activities are logged for auditing purposes. I don't believe there is any facility for suppressing log statements nor do I believe one should exist. Should a method exists consider the following: [LIST] [*]User develops a script that generates a sales order and bills items to customers credit…
-
The book I recommend is Beginning Javascript 4th edition by WROX. ISBN is 978-0-470-52593-7. Not only does it cover basics, but it also has served me well as a reference too. One thing I have found with Javascript/Suitescript programming is that alot of the book material you will cover in javascript courses/books/tutorials…
-
Turns out per NS support this functionality isn't present directly and currently has an enhancement request filed. What I have done as a work around is create a saved search with general criteria and wrote a function to further filter the search results based upon parameters passed to the function call.
-
Does anyone know the answer to this?
-
To be honest we abandoned the script in favour of re-writing the entire backend and business logic using SuiteTalk for integrations to our various locations and market places and suitescript for NetSuite logic. The ultimate result will be to keep realtime inventory in NetSuite that was only being updated on an intermittent…
-
That would be why. Thanks Oliver.
-
There is an enhancement for memorized transaction support: 117268 Its probably not a 100% match, but its the only suitescript memorized transaction enhancement request
-
This is part of a user event script that we have that fires before submit, although you could likely add it into the form code section. Make sure you edit the function accordingly; i.e. we have an override check box that we pass the value in, as well as a separate logger function
-
We use a script for this: /** * @param (boolean) locationSwitchingOverride * @param (number) numLineItems * @param (string) bodyLocation * @param (boolean) debugEnabled * @function * @description * Force line item location - May 28th 2014 * Logic provided by: Operations * Description: Force line items to have the same…
-
I just reported a case this morning with scheduled scripts showing the same behaviour - 53 minutes for the script to start in one case. I'd suggest opening a case with support if you haven't already
-
Celigo has an Amazon settlements module - We're in the very early stages of reviewing it ourselves
-
I think you'll need to do it via suitescript - specifically the Application Navigation API. Check out the help on nlapiSetRedirectURL. You may want to set it to an afer submit script to redirect it to itself.