Add Table To Offline Profile
Internal mobile-app workflow read and executed only by mobile orchestrators to add one...
Install
npx skills add microsoft/power-platform-skills --skill add-table-to-offline-profile -g -a claude-code -y- Repository
- microsoft/power-platform-skills1.1k
- Category
- Engineering
- Updated
- 4d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Internal mobile-app workflow read and executed only by mobile orchestrators to add one Dataverse table to an existing Mobile Offline Profile.
Shared instructions: shared-instructions.md, read first.
References:
- dataverse-offline-api.md §4 + §7, POST item + PATCH selectedcolumns
- offline-profile-reconciliation.md, the
schemaColumnsbaseline written in Step 7
Add Table to Offline Profile
Add a single table to an existing Mobile Offline Profile. Most common flow: user ran /add-dataverse to add a new table to their app, now wants that table available offline too.
Equivalent to running /setup-offline-profile and seeing the existing profile (extend-mode), but skips the per-table questionnaire for the tables already in the profile, only configures the new one.
Invocation context and root binding
This internal helper is always a child invocation. Before any project read or
command, execute app-working-directory.md.
Require the owner's absolute working_dir; --working-dir, when supplied, must
identify that same native-canonical root. Missing, relative, or conflicting root
context returns NEEDS_CONTEXT before project access; an inaccessible directory
is BLOCKED. Never use the launch cwd or introduce another root resolver.
