https://netsuiteprofessionals.com logo
Join Slack
Powered by
I have a custom segment that users want mandatory ...
# accounting
a
I have a custom segment that users want mandatory at the line level. I checked the setting on the custom segment to make it mandatory, which works, however when adding an Item Group to a transaction, it is expecting the custom segment to be populated on the EndGroup line. Unfortunately the Custom Segment doesn't automatically carry from the Item Group header to all of the components at the line level (like, say, Location does) - and also, users aren't allowed to edit the EndGroup line to set it. Seems like it's just not possible to make custom segments mandatory at line level if you are using Item Groups - has anyone else experienced this and found a workaround?
Obviously I know we could write scripts to validate the line upon submission to enforce the custom segment is set that way, but allow for endgroups to be empty, but I was really hoping to avoid more scripts here.
k
Yeah... I think you're gonna have to script for that use case
cause you can't modify the end of group line
Though generally - I tend to address these things via exception based reporting rather than physically making them mandatory
a
man if i had a nickel every time i suggested exception reports to this client...nope, they are adamant about validation on the front-end
you'd cringe at the number of client scripts we have for them
k
Ah, Dummy proofing their account.
a
bingo
k
That's fine if they want to keep spending the $$$ I suppose
and don't care about when they go live
though I'd imagine you need to start combining client scripts instead of making new ones
which is more $$$
a
we've started doing that iteratively
k
Yeah, master client script of all the "finalized" scripts, and then your test client scripts that aren't? haha
a
basically
entry point client scripts, and single client script library file
but when developing new ones, they get their own unique script and later are moved into the centralized model
need to start moving some workflow logic over to scripts to increase consolidation there as well
k
fun fun
a
anyway i opened a support case...but i'm fully expecting them to just tell me to use a script. ugh
k
So I'm guessing they told you to just use a script, right?
a
Haven't heard back yet actually! They are being very slow
k
"this is a how to question, and not covered under your support agreement"
a
most likely
Got another email back today "Good day. I am still working on this case. I will provide an update once we have a working solution."
i hope (foolishly) that this means they are realizing this is a bug and are working on fixing it
🤡
netsuite 1
k
Incoming thursday night hotfix that breaks something else
a
Yeah probably
k
You still working? I might have stumbled on an answer to your issue
@al3xicon
Try unchecking this box - it hides the group item and the end of group item from your SO as you enter the transaction
a
Thanks man I will give that a shot on Monday...I admit I havent played with that one in a while but was focused on the other checkbox recently. The print components one
FYI I tried that - would solve the issue but wouldn't work for the client because if unchecked, it forces the other box to checked - they don't always want to show components on printed forms when using Item Groups - sometimes want to obfuscate and show header line only
k
How are you populating the custom segment?
a
Manually for now on the line items
k
oof. Sounds like script is the answer then
a
yeah until NS fixes the issue, they still haven't gotten back to me. of course i'm not holding my breath, and the client is getting impatient so we're about to queue up the script work
k
Side note - did you know it's possible to inherit the value from the group item and apply it to the lines within automatically?
i.e. fill it out on the parent item before hitting submit and it'll flow to all the lines
a
yes - though that actually doesn't work for custom segments ironically
works on standard segments like location and on custom fields
but not my custom segment for some reason
k
Check this field on your custom segment setup: STORE WITH ITEM GROUPS
I just learned about this field while working on something for a client - which is how I stumbled on a potential answer for your question that you didn't like. Haha. Though - that field requires that the start/stop lines be displayed to work
a
oooh
that's a big miss on my part, trying now
what is weird is that was unchecked for me but was behaving as though it was checked
tried checking, didn't change the behavior, trying a log out / log in now to be sure
yeah no matter what i try it doesn't seem to make a difference in the behavior, odd
k
You might have to completely recreate the custom segment
It applies to the field definition on the column - I've had challenges with making edits to custom segments and seeing the changes applied correctly
a
ah - yeah i have too
maybe i needed a harder cache clear
4 Views
Open in Slack
PreviousNext
Powered by