Mohammed Rizwan Azam

We know we have some inconsistencies in how prepayments work and we know we are very inflexible when it comes to exchange rates and debits/credits not matching exactly at invoice proposal posting. 

Microsoft internal reference - 804154

Microsoft reference FinOps - 875531

we have worked on the table records and noted below bug in the code, could you please help us to fix this bug. 

Generally the RecId and RevisionIds follow an incremental pattern which the query below (even you mentioned in repro doc) also assumes.

As validated from the customer data this assumption in below query is incorrect. The same we can reproduce by altering the RecIds in standard env.

while select RecId from budgetRevision

      join RecId from projBudget order by budgetRevision.RevisionId

        where projBudget.RecId == budgetRevision.ProjBudget

          && projBudget.RootProjId == projId

          && budgetRevision.RecId <= this.RecId

Now as of this incident, we can mitigate it by correcting the RecIds of Revisions to follow same order as RevisionIds and all other tables where it is referenced.

However as we have the correct data in Details View (by clicking on Edit for each revision), I think it's better to fix this query itself.

Microsoft Reference - FinOps - 875531

Project Budget Revision difference between Front end View vs. Detailed view - table rec ID overlap issue

we have worked on the table records and noted below bug in the code, could you please help us to fix this bug. 

Generally the RecId and RevisionIds follow an incremental pattern which the query below (even you mentioned in repro doc) also assumes.

As validated from the customer data this assumption in below query is incorrect. The same we can reproduce by altering the RecIds in standard env.

while select RecId from budgetRevision

      join RecId from projBudget order by budgetRevision.RevisionId

        where projBudget.RecId == budgetRevision.ProjBudget

          && projBudget.RootProjId == projId

          && budgetRevision.RecId <= this.RecId

Now as of this incident, we can mitigate it by correcting the RecIds of Revisions to follow same order as RevisionIds and all other tables where it is referenced.

However as we have the correct data in Details View (by clicking on Edit for each revision), I think it's better to fix this query itself.