Sorting Date Issues - Inventory Transaction History per Part

Hi.  Can you provide a print screen that shows your search criteria?  This will help.  Please review and advise when you can.  Thanks!  Jane

Thanks for the reply, @Jane Perry.

I queried for only the part number.  No other search parameters were used.  I omitted the actual search value as it is unique to a customer’s environment.  

Please let me know if you have any suggestions or a ticket must be created.  

Hi @astfarazt 

I faced the same issue. However the following steps worked for me.

1. Sort creation time column descending.
2. Click on the kebab button on creation time column and freeze the column.

3. Then sort the created date column descending. 

Thanks for the feedback.  Although, this seems strange.  Is freezing the column a requirement based on how the software was developed or is this just a workaround?

Freezing the column isn’t the key to the proper sort, however the order of doing the sort is.  You must sort by time first then by date in order to get the records aligned as you want.  The randomness of the records just doing date can’t be relied on to get the records ordered as desired.

This is actually true of most databases, the order of records in the table can’t be guaranteed to follow a time pattern, rather it is the primary key of the table that dictates that.  In the case of transaction history, unless there is only one site involved and only one time zone for the sites, it is very possible that the transactions look out of order by date when they are in fact sequenced by the transaction history ID.

Our users are reporting this is an issue in this screen.  I still think adding Transaction History ID added to this screen would resolve the issue...

@PRODQ that or adding this which is in the overview page would do it.

matt.watters wrote:

@PRODQ that or adding this which is in the overview page would do it.

 

Gets my vote!

The date created won’t work for multi-site instances where the sites are not in the same time zone.  We have transactions in four different time zones currently and will have eight when all sites are live, so date and time created is relative to the time zone where the transaction occurred.

Transaction history ID is the only one that would properly sequence across all sites.

I’m all for Transaction ID ...