Dynamics Community Forum Thread Details

D365 - Quality Update for 10.0.34 (on-premise version)

We experienced an issue with quality update to version -> 10.0.1591.89. We have issue with dbsync

Anyone has that error? I know what it means, but i use standard packages from LCS so this is a standard

I got a different DBSYNC error, but with cloud version not on-prem.

Severity   Code   Description   Project   File   Line   Suppression State
Error       Log level - Error | Infolog diagnostic message: 'Specified field RemittanceDiscountLedgerDimension of datasource BankAccountTable does not exist in the database or the configuration key on the field or on Extended Data Type used by the field is off. The view BankAccountTableBiEntity can not be created in the database.' on category 'Error'.           0
Error       Log level - Error | Infolog diagnostic message: 'Specified field InvoiceRemittanceLedgerDimension of datasource BankAccountTable does not exist in the database or the configuration key on the field or on Extended Data Type used by the field is off. The view BankAccountTableBiEntity can not be created in the database.' on category 'Error'.           0
Error       Log level - Error | Infolog diagnostic message: 'Specified field VatDueDate_W of datasource TaxTrans_W does not exist in the database or the configuration key on the field or on Extended Data Type used by the field is off. The view TaxTransDeclarationDetailsView can not be created in the database.' on category 'Error'.           0
Error       Log level - Error | Infolog diagnostic message: 'Specified field RemittanceCollectionLedgerDimension of datasource BankAccountTable does not exist in the database or the configuration key on the field or on Extended Data Type used by the field is off. The view BankAccountTableBiEntity can not be created in the database.' on category 'Error'.           0

The real frustrating thing is that this was the same error after updating to 10.0.32. There was a fix for it in the QU for 10.0.34, but I am on the latest QU for 10.0.34, and the error still persists.

Sorry it's not a solution, but simply highlighting a broader problem that needs urgent attention.

Quick Links