For example, we have invoice history back to 2011.
A user can enter a wrong Invoice Date.
They can also enter a wrong Transaction Date.

I like to pull a report of every invoice that was updated on a particular date.
After our upgrade on 5/30/2015 all my "Date Updated" is 5/30/2015.

So when I ran a report to pull everything updated from 5/27/2015 through 6/2/2015,
I got a 39,000 page report starting with invoices from January of 2011.

The date updated is also useful in the Inventory Transaction History for sequencing the transactions in the correct order -- the order in which the updating took place.

So technically the upgrade/conversion re-wrote the record on 5/30, but is that really what the date updated should represent? I don't think this information should be destroyed by an upgrade.

And if I'm the only one in the entire world who is actually using this date, I still think it is bad form and wrong in principle for it to change.

Thank you.

Comments

  • I need to amend this. It may only be the AR_InvoiceHistoryHeader.M4T.
    Haven't checked everything yet but I really got nailed by Invoice History.
    Inventory transaction history looks OK. AP Invoice history is OK.