We are on 11.0.0.32 GHR. We parse the XML history tables into custom views so that our end users that utilize Crystal and SQL writers can access historical data easily (we do not use Infor reporting tools at this time). We discovered that if a transaction is keyed with a future effective date, then another transaction is keyed prior to the effective dated row commits with an effective/entry date prior to the future effective date, it enters the future dated row into the middle of this row. In the XML, it is a hot mess and does not process the rest of the entries. We end up with data that just ENDS historically. Has anyone else encountered this and/or have a solution as to how we can fix it?
Example:
Keyed: 9/18/2018 Effective: 9/30/2018
Keyed: 9/24/2018 Effective: 9/16/201
Snippet example: field name = "Position" t = "1" s = "9'<'entry applied="2018093004062164" timestamp="2018091812415794" actor=... You'll see the entry applied does not come at the of the previous row but rather the middle in a random spot.