So far, the only method that works appears to be a Client script, however we want to default certain checkboxes, regardless of how they are created, whether via SuiteTalk, CSV, UI, or script. Every other field type can be defaulted to a value, but I have tried T, true, Y, and yes, and none of them have any effect on checkboxes

If the fields are created on the fly, meaning added to the form on beforeLoad, those fields are considered ghost fields, they are not real fields until you save the record, therefore other beforeLoad events would not be able to find them (if I remember correctly you can't use them in searches neither). You can try triggering this beforeLoad to default the fields as the last beforeLoad event in the execution stack but I think it would not work.

So, it’s a standard record and standard field (

customerdefault

on

billingaccount

). We want to be 100% sure it’s always unchecked. Sometimes, it gets checked automatically, though not consistently. I can set that value after pageInit in a client script, but in beforeLoad, setting it does not seem to have any effect.

Have you tried

false

Yes. I should add that I was just doing the T and true for testing to see if I could get it to change

beforeLoad should work specially with native fields... I would recommend to turn off anything else on that record and try your beforeLoad script, because anything else checking that box (Workflow) or Client Script is going to happen after the beforeLoad giving you the impression that your beforeLoad did not worked...

F / false don’t work either. It either checks itself, or doesn’t based on NetSuite’s whims.

Is this during a

CREATE

event or an

EDIT

event?

during Create

Weird….

I don’t know. But, in our Client script pageInit, we have this:

context.currentRecord.setValue({ fieldId: 'customerdefault', value: false });

@jen That is a good call, some native fields trigger certain postsourcing events and also built-in client logic, so if that is the case @scottvonduhn your only option is a Client Script. You can test this by creating a custom checkbox field and test your beforeLoad script, if it always works, then you know there some NetSuite mambo chambo going on...

But the equivalent line in the UE beforeLoad does nothing:

context.newRecord.setValue({ fieldId: 'customerdefault', value: false });

mambo chambo

…..?

Mambo Jambo... my English(Spanglish) is all over the place...

the beforeLoad not working on

CREATE

is what leads me to believe something out of your control is happening afterwards

message has been deleted

yep. and the problem there is we can’t rely upon the client script in non-UI contexts. though I guess the beforeSubmit will still be our backup / last hope

You can do a combination of Client Script only for the UI and then UE (beforeSubmit) for all other contexts

I like how the various spellings of mumbo/mambo-jumbo/jambo have obscured and confused this thread

the bad thing abotu that check box, if the record is saved with it checked, it can never be unchecked later. And it has serious effects upon all manually created invoices, credit memos, and cash sales for that customer forever after

so I’m not familiar with this checkbox in particular, but is it only unticking itself when the customer already has a billingaccount set as default?

which is why we are so paranoid about a little check box. We ave had to abandon customer records we have used for years, and create new/duplicates ones, just because of it

like when this is an additional billingaccount?

The problem with it, it seems to offer no real advantage: if you create a new Subscription for a customer that has only one Billing Account, then it chooses that one automatically.

does NS force you to have exactly one billingaccount set to default for a customer?

But, if it gets checked, then SuiteBilling takes over for manually created transactions and messes with date fields, due dates, and revenue elements, and we can’t have that

right right

we basically never want any to be default, given that it confers no benefit to us, and only hurts us in many cases

yeah

We’ve already gone the NS support route, and even NS PS and our ACS rep, and no one has any solution for us, other than to tell us that we should never be creating any invoices, credit, or cash sales manually if we have SuiteBilling. And, why would we dare do such a crazy and unexpected thing.

agreed

Have you tried doing it in BeforeSubmit instead?

yes, and it does work there too. I guess I am just uncomfortable with it being checked the whole time, and then relying solely upon the beforeSubmit, especially since this one checkbox can essentially corrupt an entire customer for us.