Any suggestion on how to resolve this error while deploying the service update to a build Instance. Log level - Error | Managed Data Sync Entity Worker encountered an exception, but is continuing because ContinueOnError is true. View Name and ID: 'SubledgerJournalAccountEntryView(1897).' Exception: System.InvalidOperationException: Selected view field: 'FinTag' with data field : 'FinTag' cannot be found from underlying query's table 'SubLedgerJournalAccountEntry' on view: 'SubLedgerJournalAccountEntryView'.
-
DB Sync Error when upgrading to 10.0.39Thank you for your responses. I was able to figure this out. The issue was the build Instance had errors on the compile. I had to fix those and the DB sync worked.
-
DB Sync Error when upgrading to 10.0.39Almost always when I've had this error, I've had models which needed to be built on the environment. As this is a build environment, that shouldn't be the issue. Check packages local directory and the packages local directory backup locations on your build environment. If either have any custom models in. they need to be deleted. These will be pulled from source control every time you build, and shouldn't persist on the environment in either location.If all else fails - its an Azure CHE, its not worth wasting time investigating, provision a new build environment on 10.0.39 and delete the old one.
-
DB Sync Error when upgrading to 10.0.39Hi,
Please check if the method described in this blog is available.
https://www.cloudfronts.com/blog/d365-enterprise/d365-finance-operations/deployment-failed-in-lcs-because-of-db-sync-error/
Best Regards,
Hana
Helpful resources
Quick Links
Subscribe to
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
Leaderboard
Andre Arnaud de Cal... 283,183 Super User
Martin Dráb 222,733 Super User
nmaenpaa 101,138