Best Of

Gia My "Mei" Luc

As others note, without explicit limitation in SuiteAnswers & the reference to the same behavior as Departments, I would agree the list in a custom segment could be as long as necessary. The UI performance would mimic any excessively large pick list selection and may be annoying.

Another consideration is mass general ledger related processes (revaluations, rollups, etc). Mass processes generally have to process through every unique combination which would add a bit of processing time.

While custom segments are a great NetSuite feature, I would first scrutinize the real need to add the attribute to the general ledger.

Does the attribute apply to all posting transactions across all modules?

Can you accomplish the additional attribute with a custom "field" used in searches, reporting, Analytics in lieu of a custom segment in the general ledger?

I would brainstorm the absolute need to put the attribute in the general ledger as a custom segment. If you still think it needs to be on every general ledger transaction, go ahead and create it but I've found I can accomplish my need through an ordinary custom field with a custom list and even dependent list selection limitations…

I hope this helps.
Best Regards,

I am working on getting the screen shots from the 2 employees with the issues.

I found the solution.

I removed the transactions tile from the personalization within the vendor dashboard and added list - transaction. That seems to have cleared whatever settings she had applied to the transaction tile.

Thanks again @Pierre_Plourde ! Appreciate the help.

Hello @Gia My "Mei" Luc,

Thank you for your question.

I could not find a documentation nor related cases filed that specifies the number of values present in a custom segment before they encountered performance issues. I think it would be best to ask our fellow community members if they have any ideas.

Tagging here some of our top contributors:

@Tigran Shahnazaryan @Brian Stisser @Hormese Paul @Amanda Edwards @CDuf @Midhun Nath