Prism Dataset Load Fails with "Failed While Retrieving Data From the Source"
What it means
A Prism Analytics integration that loads data from a custom report into a base table fails for a specific user even though that user owns the report, the table, and has a Prism security group assigned. The failure is a security domain gap combined with how the report is being tested, not a data problem.
Troubleshooting
- Confirm the failing account's Prism role assignments include both Prism Admin or Prism Writer and the Prism: Manage File Containers domain; owning the report and table alone doesn't grant the file-container access the load step needs.
- Check whether the load was tested via a proxy or impersonated session rather than the user's own direct login; several reported cases only failed under proxy and succeeded once the actual user logged in and ran it themselves.
- Re-run the load with the user logged in directly (no proxy) after confirming the domain grant, to isolate whether the fix was the security domain, the login method, or both.
- If it still fails, check whether pending security policy changes for the added domain were ever activated, since an unactivated grant behaves identically to a missing one.
Have the actual user log in directly (not via proxy or impersonation) and re-run the report-driven load once the Prism: Manage File Containers domain is confirmed on their security group.
Add Prism: Manage File Containers to the standard security group template used for anyone who owns or maintains Prism-enabled custom reports, and document that proxy sessions are not a valid way to test Prism data loads, so this doesn't get rediscovered per-user.