Any reason to use one over the other if I am looking to uniquely identify a line item?

line is unique within a certain transaction, line unique key is unique among all transactions

depends what you want to use it for - if you want to build a unique key that is visible to the end user (we had such a case last month), you need to take into account that

lineuniquekey

is a number such as 54883900 and can easily jump with hundreds; as battk says, if you want "uniqueness" within the transaction, just use `line`; if you need it among all transactions, use either

lineuniquekey

or

transaction id + '-' + line

I've always used line - looks like that was the correct choice.

What would be the best way to go if you would like to identify a given line across multiple transactions? For example, a given line in the PO, that will also appear in the item receipt and in the bill (once the PO is transform). Not sure if 'line' will fit this purpose, as I wonder whether there is an use case where, in a PO, line '2' could be line '3' in the bill. I have check 'lineuniquekey' but I see is fully unique, so it is not replicated in other transactions that come from that first one.

make your own custom column, and set up the column to apply to the transactions you want linked

that's an interesting solution. So I presume the custom column with the unique value should be created at PO creation. How would you create it to guarantee the uniqueness of the value to be set in the column? Do you think is feasible to just try to map the lines with a combination of matching values that are present in the order already? As the above solution might get a little tricky because of the mention case and maybe some others

depends on your requirements for the id

what do you mean with line level exports? In my case it would be a custom record that contains no field, so only the automatically added id. Am I right? Still I would like to avoid this path and try what we discuss in the other thread, as I believe is the case that you are referring, only one level away from the parent

typical integration technique for sending data out of netsuite is to mark a checkbox to indicate it was successfully exported

ah, that makes sense, seems like the best way to go for that kind of cases. In my case, I will try to make it work with the orderline. If not, I think I will resort to the custom record creation per line, using the id assigned by NS, so I do not need to think about the uuid creation

I use a monotonically increasing integer for unique line identification.

How do know the last number that was use? I believe what you are saying is that what you use is not a custom record, but simply an integer in the line of a given transaction.

yes, IIRC I add a user event on the originating transaction to set the next value

Very interesting, thanks for sharing! I definitely see a lot of value having a custom unique line identification in parent transaction that you can track in child transactions

yup, while NS provides it in some transaction chains, there's nothing that spans all combinations.

oh hey, its supports removed lines now, thats improved from the last time i saw that code

my bad 🙂