You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can't see any notes in the Deployment Guide on how to align the Azure backend SQL database with the optional sample data installed with the Fundraising and Engagement solution?
Is there a list of entities that must be synchronized with the backend in order for the sample system to work?
The text was updated successfully, but these errors were encountered:
We have forced a sync via the plugins by 'touching' each of the records, this has highlighted that some of the sample data have missing mandatory fields that throw error in the plugins.
To avoid sequencing issues we created T-SQL scripts to drop and re-create the FK constraints.
I used flow to force sync (see Paul's post above)using parallel execution to touch several entities at the same time.
This was logged in Application Insights:
A second operation started on this context before a previous operation completed. This is usually caused by different threads using the same instance of DbContext. For more information on how to avoid…
So it looks like there's an issue with the way the API is coded to share its database context(s).
@paulhasell and @Steve-Dawkins thank you, we are actively working on making this a less manual process. We will keep you updated. If you run into any other challenges please file a support case here. We are unable to handle support cases via GitHub. Thank you!
I can't see any notes in the Deployment Guide on how to align the Azure backend SQL database with the optional sample data installed with the Fundraising and Engagement solution?
Is there a list of entities that must be synchronized with the backend in order for the sample system to work?
The text was updated successfully, but these errors were encountered: