What problem does it solve?
A Mobile Offline Profile created in Dataverse does nothing until users or teams are explicitly bound to it. This Skill closes that gap by assigning (or unassigning) users and teams to an existing profile so their mobile apps actually receive offline sync.
Core Features & Use Cases
- Membership assignment: POSTs
usermobileofflineprofilemembership and teammobileofflineprofilemembership records via the Dataverse Web API, with support for --user, --team, --me, and --all-app-users flags.
- Idempotent diffing: Discovers existing memberships first, then presents a single confirmation gate showing adds, removals, skips, and unresolvable entries before writing.
- Verification and recovery: Re-queries memberships after writes to confirm the diff applied, and supports safe re-runs plus
--unassign-* flags to undo bindings.
- Use Case: After creating an offline profile for a field-service app, run this Skill with
--all-app-users so every system user receives the profile on their next mobile sign-in.
Quick Start
Ask the agent to assign the current offline profile to specific users or teams, for example by providing UPNs or a team name to bind to the profile.