Thanks, I tried that and used the {datecreated} field that it suggested, but I still get the same error. This is the full formula I'm using. CASE WHEN TO_CHAR( {customer.custentityuk_premuim_shipping_expiry} ) > TO_CHAR( {datecreated} ) THEN 'Y' ELSE 'N' END (forgot the "customer." on the original post)

Excellent, that works fine when used in a Saved Search. Unfortunately though, it then won't transfer to a Custom Trans Body field without erring. If I leave it as it is. CASE WHEN (({customer.custentityuk_premuim_shipping_expiry}-{datecreated})>0) THEN 'Y' ELSE 'N' END Then I get ERROR: Field Not Found If I adjust the date…

Thanks for this, "createddate" now returns a date/time. One problem though, it's in the wrong time zone! The date/time returned by "creadteddate" is 2010-05-08 00:41:00.0 while the date correctly logged in system notes is 8-May-2010 8:41 AM - so I'm 8 hours out! Is there an option for pulling back the date correctly…

Is this something I should now take up with Support?

The "customer.custentityuk_premuim_shipping_expiry" is a date field. I've done a straight field comparison using "CASE WHEN {customer.custentityuk_premuim_shipping_expiry} > {datecreated} THEN 'Y' ELSE 'N' END" But this gives me an "ERROR: Invalid Expression" message

Load a custom CSS stylesheet in your browser preferences (if you can), and use the following CSS style; #devpgloadtime { display: none; } Not fully tested this on all pages, etc - but seems to work OK. Mark.

Just curious, has anyone ever found a solution to this issue?

Take a look at this SA article about logging when a transaction is printed. https://netsuite.custhelp.com/app/answers/detail/a_id/24776/kw/24776 You can set a Workflow Event Type to Print, and let a script do the rest.

Anyone able to shed any light on this? NS Support say there's not an issue, although they won't explain why we're getting the error:(

Looking through our current SSL certificate - I've noticed that it's TLS 1.2 But the help centre states "nlapiRequestURL supports SSL 2.0, SSL 3.0, and SSL 3.1/TLS 1.0." Is this going to cause this invalid certificate error?

I've not had any real feedback apart from "We're looking into it" Trying to figure out how not being able to set hidden values would create the issue we're seeing. We're asking for the InternalID, and we're getting the wrong number back.

Is there any update at all on this? I've been emailing support for 2 days now, but not a single reply - I'm not at all impressed by this. This is a S1 defect, clearly caused by Friday's eFix update - can we get a resolution to this ASAP.

Can you please attach me to this defect so I can see the latest progress.

So, 5 days after this first occurred - we have an S1 defect but still no resolution!

Fix released

Is there any reason a active in-use script would have no data in the execution log? We've removed all date criteria from the custom view.

Doh! Apologues, I didn't write the script - and obviously made too many assumptions!

The deployment is set to Debug, and the view has no criteria set at all and the filter is set to all. So I would expect to see something. Probably missing something very obvious :(

We do it exactly the same way, but the one thing we struggled with at first, was selecting an div element which coloured the page, but without coloring too much. We ended up using the "detail_table_lay" element

Here's an update - I changed the code to the following: function postSourcing(type, name, linenum) { if(type == 'item' && name == 'item') { var itemId = nlapiGetCurrentLineItemValue('item', 'item'); if(itemId){ var purchasePrice = nlapiLookupField('inventoryitem', itemId, 'cost'); nlapiSetCurrentLineItemValue('item',…

You will need two scripts to handle these : [LIST=1] [*]Client side script This script will be used to automate the values while the user is entering the Transfer Order in the UI. You will need to have a trigger on Post Sourcing event. function postSourcing(type, name, linenum) { if(type == 'item' && name == 'item') { var…

Sorry if I'm missing some subtlety in the question, but you simply add it as you would any other item, the only difference being that you need to supply to/from/message for the item.

It would seem that you cannot use RESTlets with user roles which are "Web Services Only" roles - and my own experience also has shown that there are issues also using an admin role. I ended up creating a specific RESTlet role, and that's been working fine.

Could this not be done with a simple workflow, using the Hide Field action?

Does anyone know whether this same defect is also affecting emails sent out through the Customer Record? We're finding that the "reply to" address for all communications manually sent via the customer record, now contains the employees email address and the NetSuite case email.

On a similar topic, is it possible to VOID an order via SuiteScript?

Has there been any progress on this issue? We came across the same problem today, and our way of getting around this has been to change the customer default shipping address immediately before setting the shipping - that way the correct Tax Code is being used. However, this is far from perfect.

I need to be able to concatenate multiple custom fields into a new custom field - this will be done on an Inventory Item. Two questions; [1] Can ns_concat() do this for me [2] Can I somehow use a wildcard to include multiple fields IE: "take all fields starting with 'ABC' and concatenate them into a new string" Thanks.

Have you thought about trying it this way... Create a Div called <Div class="hide-<%=getCurrentAttribute('item','custitemretailhide')%>"> Then in your style sheet use .hide-True {display: none}; Mark.

Just to clear up any confusion, can you use a "getAttribute" within JavaScript, or do you indeed need to hide it in a form field first? Thanks. Mark.