I’m trying to understand whether this is expected Dataverse/TDS behavior or a bug.
Facts:
- `userquery` is a user-owned table.
- TDS uses the Dataverse security model for data access.
- In my environment, personal views owned by an inactive user do not appear when queried through SQL 4 CDS / TDS.
- However, the XrmToolBox Personal User Views Migration tool is able to find those same views and reassign them.
- After reassignment to an active user, the views do appear through TDS / in `userquery`.
- `createdby` still shows the original inactive user after reassignment.
Question:
Is it expected that `userquery` records owned by inactive users are excluded from the TDS endpoint, even though they still exist and can be enumerated/reassigned through other APIs/tools? Why don't these continue to appear in the 'userquery' table?
More specifically:
1. Is this due to documented TDS/security behavior for user-owned personal artifacts?
2. Is there any official documentation covering TDS behavior for personal views (`userquery`) whose owner is inactive?
Repro steps:
1. User A creates a personal view.
2. User A is made inactive.
3. Query `userquery` over TDS / SQL 4 CDS -> view does not appear.
4. Use Personal User Views Migration tool -> view is visible and can be reassigned.
5. Reassign to active User B.
6. Query `userquery` over TDS again -> same view now appears.
Environment:
- Dataverse online
- SQL 4 CDS over TDS endpoint
- XrmToolBox Personal User Views Migration tool
- Querying as System Admin
I’m mainly trying to determine whether this is expected platform behavior, a TDS limitation, or a bug/inconsistency between endpoints.
