Runtime Behavior and Access Considerations
Cross Application Data Sharing routes requests between consumer and provider applications at runtime based on the current subscription state, permissions, compatibility status, and runtime configuration. Compatibility validation helps identify package-version or schema mismatches between applications, while runtime access behavior depends on the current provider domain exposure and authorization state.
Understanding Query Behavior
When your application queries a shared type at runtime, the query is proxied to the provider application. Data is never replicated to the consumer, it is fetched live on each request.
- Authentication or authorization failures: If access to a provider domain becomes unavailable because of credential, subscription, or permission changes, requests against the shared domain may fail at runtime depending on the current application state and operation being performed.
Schema Evolution and Metadata Sync
Provider and consumer applications can continue evolving independently over time. Cross Application Data Sharing includes compatibility validation to help identify package-version or schema mismatches that could affect interoperability between applications.
The current implementation validates compatibility between the consumer and provider applications and surfaces the results in the Compatibility column of the My Subscriptions tab. Compatibility validation is informational only and does not block subscriptions or data access.
Compatibility validation can be triggered on demand from the Compatibility column in the My Subscriptions tab. The validation process compares the consumer application against the provider application's current domain exposure and compatibility metadata at runtime.
When provider applications update registered domains, consumer applications may need to rerun compatibility validation and review downstream application behavior to evaluate the impact of updated domain definitions.
Known limitation: Cross Application Data Sharing compatibility validation applies to entity types only and does not support custom interface types.