Can I get some people to endorse my enhancement? E...
# suitescript
t
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.
b
that is going nowhere when the alternative is to do a search or query instead
t
you can't write to a record using a search or a query. This issue is that in a write context you can't verify a line you are writing to has the same unique line key value that you are trying to reconcile to
a
This is obviously a defect, you should keep pushing them to recategorize it, but happy to vote on the enhancement for you... we should do this more often! people power! 🙂
b
transaction lines also have line id or sequence numbers that you can match
a
in the context of a single transaction sure... but if you're running a map reduce for many transactions and cross referencing from an initial dataset using the PK from the transaction lines table seems like the obviously correct way to do it.
b
starting from a query means you likely already have access to the join with the unique key / line id / sequence number in it already
m
Anybody been able to reconcile Item Fulfillment or Item Receipt lines with searches? I have had a difficult time with reconciling those with unique values.
t
@battk Some transactions have multiple sublists, others don't. Some have items some have expenses. Do you use line # and item for one sublist? What about credit card charges? Having the primary key there is 10,000x easier than a heuristic identifier for each transaction type. I'm not saying its impossible its just much more effort and complexity for a solution that could be solved by exposing lineuniquekey which is a hidden field with no negative impacts.
b
it probably is easier, but my point here is that defects with workarounds have very low priority
enhancements with workaround lower
t
Thats why I'm looking for endorsements.
m
Does it require a suiteanswers account? (to endorse)
m
Oh yeah it requires a role that I don't have.
t
😞