What problem does it solve?
Enabling offline mode for a Power Apps mobile app requires manually creating Mobile Offline Profile entities in Dataverse — defining per-table row scope, relationships, column selection, and sync intervals — a tedious, error-prone process normally done through the maker portal.
Core Features & Use Cases
- Guided 3-gate approval flow: An architect agent designs the profile from your data model manifest, then you review and adjust table scope, sync intervals, and columns through structured prompts before anything is published.
- End-to-end Dataverse provisioning: Creates the mobileofflineprofile, per-table profile items, and relationship associations via Web API, then publishes with targeted PublishXml.
- Resume and idempotency: Checkpoints progress in memory-bank.md so interrupted runs resume from the last committed step, and duplicate POSTs are handled safely.
- Use Case: You have a field-service mobile app with visit and note tables and want technicians to access data without connectivity — run this skill to design, review, and publish a complete offline profile in one session.
Quick Start
Ask the agent to set up an offline profile so my Power Apps mobile app works without connectivity.