My Stuff
Comments
-
try typing the number followed by a %
-
If you are using a SQL formula, use NVL(fieldname, nullvalue) NVL({field1},0) + NVL({field2},0) + ...
-
A very simple script would do it. I use an aftersubmit user event like this: function aftersubmit(type) { var source = nlapiGetFieldValue('originator'); if (type == 'create' && source == 'NLWebStore') { var tran_type = nlapiGetRecordType(); var tran_id = nlapiGetRecordId(); var transaction = nlapiLoadRecord(tran_type,…
-
You're going to need a script or workflow to get a fulfillment record to update a customer record.
-
dashcraft - the script works for me, so I'm note sure what is different for you. However, in your revised script, you need to change function salesOrderContextScript(){ to function salesOrderContextScript(type){
-
Hey Tom - another way to approach this is to add a non-inventory item (named 'catalog') to the order. You could have a really simple script or workflow that would add the item to the SO if the customer has no previous sales.
-
What about locationquantityavailable, or maybe item.locationquantityavailable
-
try changing {custbody_item_no.custitem_margin} to TO_NUMBER({custbody_item_no.custitem_margin})
-
If it's a 'Free Form Text' field, you can set the 'Maximum Length'. If it's an 'Integer Number' field, you can set a 'Maximum Value'.
-
I'd suggest that you create a new, temporary field to test that.
-
Just a thought, maybe this would work - Make a 2nd pick ticket form, keeping the original form as the default. On the 2nd form, change the title to 'Packing Slip'. Then create a button that prints the pick ticket using the 2nd form, but the main form is still used for real pick tickets.
-
Not sure about labels... but the faux packing slip should be a really short script using nlapiPrintRecord
-
Make sure that there is at least one field set to display on your tab. Empty tabs are hidden.
-
The invoice is created from the sales order, not the fulfillment, so 'created from' won't work. You could try writing back to the SO from the fulfillment with a custom field, like 'Last Fulfillment' and then use that on the invoice. But I believe that you can have more than 1 fulfillment per invoice too, so it could get…
-
It's probably because one of the fields is null. You can use 'nullif' or 'case when' statements to catch it. Eg Case when {quantityonorder} is null then 0 else {quantityonorder} end
-
try this function create_case() { var company=3; //CU000001 Anonymous Customer var contact=781; //fake var due_date='7/20/2012'; var record=nlapiCreateRecord('supportcase'); record.setFieldValue('title', 'test'); record.setFieldValue('incomingmessage', 'test incoming message'); record.setFieldValue('company', company);…
-
Maybe create a bundle with your current record type, then change the id of your current record type, and then install your own bundle? Not sure if it would work, just a thought.
-
It's probably under 'status', the full field list is here https://system.netsuite.com/help/helpcenter/en_US/RecordsBrowser/2010_2/records/supportCase.html
-
There's a few ways to do it: custom records, scripts, custom fields, etc. But it would all be a lot easier if you could compare zip codes instead of cities.
-
So I'm not sure about all the formatting on the customer record itself, but you could try to sell it to your sales dept as two views: a basic customer view (customer record), and a detailed customer view (which is really a view of the custom record formatted the way you want it). The customer record and the custom record…
-
You can use a simplified 'business days', see example in this thread https://usergroup.netsuite.com/users/showthread.php?t=30425
-
You should consider making a custom record type that holds all this special info, and then relate it to the customer record 1 to 1. The custom record type can then be shown in sublists on the customer record and referenced in searches.
-
try {isdropshipitem}='T' instead
-
Try to debug it by creating & displaying a text formula equal to {isdropshipitem}. If you get a null or Field Not Available then you can track it down further
-
Thanks that's perfect.
-
Thank you that worked - kind of... Users with the same language now see the correct field labels when they 'Print' the form. However, when they 'Email' the form, it reverts to the old version. Seems like the email functionality in NS chooses the system default language. Unfortunately I never even thought to test this so…
-
{customer.parent} should work. Parent never seems to show up in the UI lists but it's there for searches and forms.
-
You could also set up a saved search that checks for inconsistencies on Sales Orders. Depending on how your business is set up, you would have to adjust what you are looking for, but for example: Type = SO Status = Open formula: Line Amount / (( standard price) * qty) < 0.9
-
If you add a transaction column field call 'Line Number' you can have a script add the number. You'll want to use the function nlapiGetLineItemCount('item'); and then loop something like this var noOfItemCount = nlapiGetLineItemCount('item'); for (var t = 1; noOfItemCount != null && t <= noOfItemCount; t++) { var…
-
Kast - We use a custom record type called "Customer Part Number" that references the item and customer records. The cross ref lists were easy to load thru csv. I've extensively scripted to allow "on the fly" additions & changes to the "Customer Part Number" records via sales orders. For example, if Customer Service is…