@al3xicon Thanks!! Let’s see if we can drive up the votes on some of these things!

Can you maybe name this upvote-enhancents?

9995 - Title: Ability to change the Item Type other than from Non-Inventory to Inventory

has renamed the channel from "enhancements" to "upvote-enhancements"

Member Line ID available via search for native accounts.. SuiteIDEA 242854 currently has 32 votes..

I have end-users asking for this all the time: #76300 - Allow dashboard content to periodically auto-refresh

For any non-US customers, you might want to consider adding a vote for "386136 APM > Ability to Change Time Zone" if, like me, you find only being able to view performance charts and logs in US time makes things far more difficult.

At the current moment you can not choose lot numbers on the sales order for kit items I heard a rumor this is changing in 2022 any way to find out

Can we please vote for Enhancement # 670076

Netsuite has inconsistent encoding for unicode characters with the webstorm suitecloud IDE plugin and this would allow a better experience

Can I get some people to endorse my enhancement? Enhancement #500563 Unique Line Key available in database but not in record for multiple transactions (expense reports, credit card charges, item receipts) NetSuite has "lineuniquekey" as the primary key for the transaction database. Every line in that table has the value and its unique. Definition of a primary key pretty much. However for some records, expense report for example, this value will be missing if you attempt to read it from the sublist at the record level. The field isn't exposed on the expense sublist despite it being visible in saved searches, analytics and suiteql. In any context that you can write to the record (suitescript, CSV imports etc...) you cannot see this value and I need to reconcile against lines so this is very annoying. When I brought this up to NetSuite they marked it as an "enhancement" and refuse to mark it as a defect and address it. Random sublists on random records have this primary database key missing and I was scolded saying "I shouldn't design solutions around assumptions". Apparently the assumption is that the primary database key is visible on all records instead of just 95% of them.