I'm curious what the community thinks in this comm...
# suitescript
l
I'm curious what the community thinks in this common scenario.. 🤔 What if you come across a NetSuite field that is unexposed in the Records Browser but you really need to use it on your script? What would you do? 1️⃣ I won't care. I will still use it in my script and just put out the fire when it breaks. 2️⃣ Build custom fields that mimic its functionality. 3️⃣ Report it to NS and wait for N years till it gets exposed. 4️⃣ Look for other ways to avoid using that field. 5️⃣ Others, please educate us what better options we have!
5️⃣ 1
1️⃣ 12
3️⃣ 2
4️⃣ 7
2️⃣ 14
a
Just added the 5 options as icons so people can easily vote. Ignore those votes in your final count 🙂
Great question by the way! I want to know the answer too 🙂
a
We have ended up mimicking the records, but that's more because we do not want all the things that NS solution wants us to do. For e.g. managing product specifications - NS way of doing things will require us to hire one more clerk, We built a custom record and some scripts that give us the benefit without the extra cost.
s
If we have no adequate substitute, we will use the field, but make a clear note that it exists but is not documented in the NFT class definition so it's seen by anyone using it.
1️⃣ 1
While I consider the records browser the 'source of truth' it is also riddled with errors
true news 1
1️⃣ 1
d
Good question. I think it would depend on what you're trying to do and what record it is. If it's a one-off solution for a single customer account I'd probably use the field. Otherwise it might be part of an add-on solution and I'm not sure what I'd do at that point.