What problem does it solve?
Dataverse tables cannot be added to a Mobile Offline Profile unless both the IsAvailableOffline and ChangeTrackingEnabled flags are set on their EntityMetadata, and configuring this manually per table through the maker portal is slow and error-prone.
Core Features & Use Cases
- Metadata Flag Updates: Sequentially PUTs EntityMetadata changes to set IsAvailableOffline and ChangeTrackingEnabled on one or more Dataverse tables, respecting the Dataverse metadata write lock.
- Idempotent Execution: Re-running on already-enabled tables is a no-op, and uncustomizable system-managed tables are safely skipped and reported.
- Targeted Publishing: Publishes customizations with a scoped PublishXml call (with PublishAllXml fallback) and verifies the flags post-update.
- Use Case: Before running /setup-offline-profile for a Power Apps mobile project, enable offline prerequisites on all tables listed in .datamodel-manifest.json in one guided, approval-gated workflow.
Quick Start
Ask the agent to enable offline prerequisites for the Dataverse tables in this project, optionally passing a comma-separated list of table logical names.