This looks like a Customer Insights - Data refresh issue with the Dataverse Contact entity, rather than a problem with the Account table or the initial connection.
Since the Dataverse data source was configured successfully and the refresh is failing specifically on:
newwaysandbox_contact
I would first check the Contact table itself in Dataverse.
A few things I would verify:
- Confirm the Contact table is still accessible in the Dataverse environment and hasn't been renamed/deleted or had its permissions changed.
- Check whether the Contact table/schema was recently modified, especially columns, relationships, or calculated/formula columns.
- Compare the Contact table with Account. Since Account refreshes successfully from the same data source, the Dataverse connection itself is probably working.
- Check whether there are any unusual/broken records or columns in Contact that Customer Insights cannot process.
- In Customer Insights - Data, try removing the Contact entity from the data source and adding it again, then run a fresh refresh.
- If possible, create a small test Dataverse table and confirm that Customer Insights can ingest it. This helps isolate whether the problem is specific to Contact.
- Check the Customer Insights task details/logs for the underlying error if a more detailed message is available.
The message “Could not load data for the entity ... due to an internal error” is quite generic, so the fact that only newwaysandbox_contact is failing is the most useful clue here.
I would also avoid deleting/recreating the whole Dataverse data source initially. Since Account is working from the same connection, I would troubleshoot the Contact entity/schema/data first.
If Contact was working previously and suddenly started failing without any Customer Insights configuration changes, check what was changed in the Contact table around the time the refreshes started failing. That is likely to be more useful than changing the Dataverse connection itself.