Data synchronization with Azure for sample data supplied with the F&E solution... about fundraising-and-engagement HOT 3 CLOSED

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.

from fundraising-and-engagement.

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).

from fundraising-and-engagement.

@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!

from fundraising-and-engagement.