Yeah I've noticed^^ It has some powerful elements but trying to make it feel modern is hard^^

FWIW we've built multiple SPA's for NetSuite.

Did you mix netsuite UI components with custom or just created your full blown custom UI widget suite for that purpose?

We've done full blown AngularJS and Aurelia mini-apps backed by Suitelets as a pure backend data layer. Works much faster than typical NS pages and you have full creative flexibility on the look and feel.

Yeah thats probably a lot easier^^ But for my usecase a full blown SPA is overkill. And so far I only needed two little DOM hacks to accomplish what I need^^

if it's really small then hack away!

The only thing that really annoys me is the inconsistency that Netusite APIs are working at. Custom fields can not be searched for when I use type BILL_PAYMENT but when I use type TRANSACTION i can. Even tho the custom fields are dedicated to bill payments and stuff like htat

oh, that's an entirely separate issue I think. Not knowing all the details, I think you were talking about transaction statuses? Well depending on what field you're looking at the transaction status is a unique set of values for each type of transaction (e.g. billpayment is different values than salesorder). I know that was a big issue in SS1 but can't remember if they've smoothed that over in SS2 or not

no its a custom field I've created

the field name dynamic thing should work. I suspect your string concatentation wasn't actually getting a string for the dynamic part

it was I even assembled it into a var and run typeof

and/or

_.toString()

on it before concatenation

as soon as I called

createFilter

with string cocatination it worked^^

If you have the code handy to paste here I'll think about it a bit more, but I know I've used dynamic field names because NFT actually depends on it.

I fixed it with the object filter syntax which works

ok, so your dynamic field name creation works?

yes just with workarounds