Client on Sage 100 Advanced 2018.4 and they have two weird data issues going on with their SO_SalesOrderHistoryDetail table.
The first issue is a line who's LineSeqNo is blank and so it can't be deleted by the user in Sales Order Entry. It appears as the first row in the grid. Not sure how this happened, i believe i can just find the next available LineSeqNo to use and throw that in there so they can delete it properly. I only found one instance of this occurring.
The second issue is a much bigger issue as it has occurred 1,300 times across all of the data in their history table. The issue is that in the history table, there are two records that share the same LineKey yet have a different SequenceNo causing both lines to show up in Sales Order/Quote History inquiry but only the last line of the two to show up in Sales Order Entry since the primary key for SO_SalesOrderDetail is the SalesOrderNo+LineKey and it has to be unique. So somehow, a line added after the first line inherits the first line's LineKey and when committed to the physical file, the second line overwrites the first line. So far, the only thing that we believe could be causing this and would likely be a bug is that the user will start a order, add some lines, and save it. Then at another period in time, they open the order, add new lines, then reorder the lines using the Move Row Up/Down buttons, and save it. The addition and reordering of lines could occur over a month's time or less.
Has anyone seen anything similar to either issue with detail and history detail tables?
------------------------------
David Speck II
Tennessee Software Solutions
------------------------------