[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699NZZFKZB0A3EX012NEDMD":3,"skill-same:01M699NZZFKZB0A3EX012NEDMD":85},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":68},"01M699NZZFKZB0A3EX012NEDMD","enable-tables-offline",null,"Internal mobile-app workflow read and executed only by \u002Fsetup-offline-profile to enable Dataverse table prerequisites for a Mobile Offline Profile.","microsoft\u002Fpower-platform-skills","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M699JVYJFB75D9JM70BN4H0Q",1149,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fmobile-apps\u002Fskills\u002Fenable-tables-offline\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"enable tables offline","offline","tables","edit","for","true","sonnet","false","app","mobile","only","profile","workflow","write","read","grep","table","Bash","setup","dataverse","2026-11-10 10:12:30",false,"---\nname: enable-tables-offline\ndescription: Internal mobile-app workflow read and executed only by \u002Fsetup-offline-profile to enable Dataverse table prerequisites for a Mobile Offline Profile.\nuser-invocable: false\ndisable-model-invocation: true\nallowed-tools: Read, Edit, Write, Grep, Glob, Bash, AskUserQuestion, EnterPlanMode, ExitPlanMode\nmodel: sonnet\n---\n\n**Shared instructions: [shared-instructions.md](${PLUGIN_ROOT}\u002Fshared\u002Fshared-instructions.md)** — read first.\n\n**References:**\n\n- [offline-profile-schema.md](${PLUGIN_ROOT}\u002Fshared\u002Freferences\u002Foffline-profile-schema.md) — entity field map (`IsAvailableOffline`, `ChangeTrackingEnabled`)\n\n# Enable Tables Offline\n\nFlip `IsAvailableOffline=true` AND `ChangeTrackingEnabled=true` on the `EntityMetadata` of one or more Dataverse tables, then publish customizations. This is the prerequisite shown in Image 4 of the maker portal (\"Can be taken offline\" + \"Track changes\") — without both, a table CANNOT be added to a Mobile Offline Profile.\n\nSequential (Dataverse metadata lock) and idempotent: re-running on an already-enabled table is a no-op.\n\n## Invocation context and root binding\n\nThis internal helper is always a **child invocation**. Before any project read or\ncommand, execute [app-working-directory.md](${PLUGIN_ROOT}\u002Fshared\u002Freferences\u002Fapp-working-directory.md).\nRequire the owner's absolute `working_dir`; `--working-dir`, when supplied, must\nidentify that same native-canonical root. Missing, relative, or conflicting root\ncontext returns `NEEDS_CONTEXT` before project access; an inaccessible directory\nis `BLOCKED`. Never use the launch cwd or introduce another root resolver.\n\nReceive `MOBILE_APP_ORCHESTRATING=1`, `orchestrator: setup-offline-profile`,\n`working_dir`, `phase`, `approved_scope`, and supplied answers. Preserve the\nselected environment ID\u002FURL\u002Ftenant and exact table\u002Fprerequisite\u002Fpublication\nallowlist. The marker is not approval. Reuse only matching current offline\napproval; a missing or changed scope returns `NEEDS_CONTEXT` to the owner.\nFor `--plan-only` or a planning-phase handoff, return the proposed prerequisite\nchanges after permitted read-only inspection, before PUT, publication, or\nartifact writes. A gate response cannot lift proposal-only mode.\n\nApply the canonical root contract to **every shell call and file tool**.\nRe-supply the absolute `PLUGIN_ROOT` and invocation context on each call; no\nprior `cd`, export, or shell variable persists. Missing values return\n`NEEDS_CONTEXT`; never execute an unresolved placeholder.\nAll linked recovery commands, re-GET verification, and retries use the same\nroot, environment, and explicit tenant. Read only absolute app-local paths,\nincluding `\u003Cworking_dir>\u002Fpower.config.json`, `\u003Cworking_dir>\u002Fmemory-bank.md`,\nand the manifest locations below.\n\n## Workflow\n\n1. Verify project & auth → 2. Resolve table list → 3. Inspect current state → Gate → 4. PUT EntityMetadata per table → 5. Publish → 6. Verify → 7. Summary\n\n---\n\n### Step 1 — Verify project & auth\n\n```bash\ncd -- '\u003Cworking_dir>' || { echo \"BLOCKED: cannot enter working_dir\" >&2; exit 1; }\nif [ ! -f power.config.json ] || [ ! -f app.config.js ]; then\n  echo \"BLOCKED: working_dir is not an initialized app\" >&2\n  exit 1\nfi\n```\n\nRequire the app's `environmentId` to match the owner's selected environment\nbefore any discovery or mutation. Use this non-persisting lookup from the same root:\n\n```bash\ncd -- '\u003Cworking_dir>' || { echo \"BLOCKED: cannot enter working_dir\" >&2; exit 1; }\nenvironment_id=$(node -p \"require('.\u002Fpower.config.json').environmentId || ''\") || {\n  echo \"BLOCKED: unreadable power.config.json\" >&2; exit 1;\n}\nif [ -z \"$environment_id\" ] || [ \"$environment_id\" != \"\u003Cselected-environment-id>\" ]; then\n  echo \"NEEDS_CONTEXT: selected environment does not match working_dir\" >&2\n  exit 1\nfi\nnode \"${PLUGIN_ROOT}\u002Fscripts\u002Fresolve-environment.js\" \"$environment_id\" --no-cache --require-tenant\n```\n\nCapture the **Environment URL** and **Tenant ID** from the resolver for\n`\u003CenvUrl>` and `\u003CtenantId>`. Pass this tenant explicitly on every helper call\nand retry below; missing or conflicting tenant context is `NEEDS_CONTEXT`.\nRequire the ID, URL, and tenant to match the owner; never switch accounts or\nenvironments to recover. STOP if not authenticated.\n\n### Step 2 — Resolve table list\n\nUse only the exact table allowlist in the owner's `approved_scope`. The comma-\nor space-separated table list in `$ARGUMENTS` must match it; `--working-dir` is\nroot context, not a table name. Missing or conflicting table selection returns\n`NEEDS_CONTEXT`; an explicitly empty approved list is a verified no-op.\n\nInspect `\u003Cworking_dir>\u002F.datamodel-manifest.json`, or\n`\u003Cworking_dir>\u002Fdocs\u002Fplan-artifacts\u002F.datamodel-manifest.json` for newer apps, only\nto verify those selected tables. The manifest is not permission to enable every\nrow. Do not discover another app's manifest or expand the allowlist silently.\n\n### Step 3 — Inspect current state\n\n**Print before starting:**\n> \"→ Querying current IsAvailableOffline + ChangeTrackingEnabled for \u003CN> table(s)…\"\n\nFor each table, in sequence:\n\n```bash\ncd -- '\u003Cworking_dir>' || { echo \"BLOCKED: cannot enter working_dir\" >&2; exit 1; }\nnode \"${PLUGIN_ROOT}\u002Fscripts\u002Fdataverse-request.js\" \"\u003CenvUrl>\" GET \\\n  \"EntityDefinitions(LogicalName='\u003Ctable>')?\\$select=LogicalName,DisplayName,IsAvailableOffline,ChangeTrackingEnabled,IsCustomizable\" \\\n  --tenant-id \"\u003CtenantId>\"\n```\n\nBuild a status table:\n\n```text\n| Table              | IsAvailableOffline | ChangeTrackingEnabled | IsCustomizable | Needs change? |\n|--------------------|--------------------|-----------------------|----------------|---------------|\n| cr123_note         | false              | false                 | true           | YES (both)    |\n| cr123_visit        | true               | false                 | true           | YES (track)   |\n| contact            | true               | true                  | true           | NO            |\n```\n\n**Hard rule:** if `IsCustomizable.Value=false` on any table, that table CANNOT be modified. Drop it from the change set and flag in `DONE_WITH_CONCERNS` — system-managed tables (most OOB) require an admin solution patch path the skill does not handle.\n\n### Gate — Approval before mutation\n\nCompare the status table from Step 3 with the owner's approved prerequisite and\npublication delta. Matching current Gate 1 approval is reused without a duplicate\nprompt. Otherwise return the status table and `NEEDS_CONTEXT: offline prerequisite\napproval` to `\u002Fsetup-offline-profile`, which owns the approval gate. Do not widen\nscope or override proposal-only mode.\n\nPlan body:\n\n```text\nThe following EntityMetadata changes will be PUT in sequence:\n\ncr123_note   → set IsAvailableOffline=true, ChangeTrackingEnabled=true\ncr123_visit  → set ChangeTrackingEnabled=true (IsAvailableOffline already true)\n\nAfter all updates, targeted PublishXml will publish only the changed tables.\n\nTables already in the desired state are skipped (no API call).\n```\n\nIf the user rejects, STOP. Proceed only with the exact approved delta.\n\n### Step 4 — PUT EntityMetadata per table\n\n**Print before starting:**\n> \"→ Updating EntityMetadata for \u003CN> table(s) sequentially (Dataverse serializes metadata writes)…\"\n\n> **⚠️ Concurrency rule — do not violate.** Metadata writes hold an exclusive lock per org. Issue one PUT, wait for 2xx, then the next. No batching, no parallel calls. Same rule as `\u002Fadd-dataverse` Step 5.\n\nFor each table needing change (skip ones already in target state):\n\n```bash\ncd -- '\u003Cworking_dir>' || { echo \"BLOCKED: cannot enter working_dir\" >&2; exit 1; }\nnode \"${PLUGIN_ROOT}\u002Fscripts\u002Fupdate-entity-offline-flags.js\" \"\u003CenvUrl>\" \\\n  --table \"\u003Ctable>\" \\\n  --offline true \\\n  --tracking true \\\n  --tenant-id \"\u003CtenantId>\"\n```\n\nThe helper:\n- Re-reads `EntityMetadata` to pick up the current `MetadataId` + `SchemaName` (both required in the PUT body — Dataverse rejects PUT without them).\n- Sends `MSCRM.MergeLabels: true` so display labels are preserved (the alternative wipes labels — never use `false`).\n- Returns `{ \"status\": 200, \"noop\": true, ... }` if the table is already in the target state (skip silently).\n- Returns `{ \"status\": 200, \"skipped\": \"uncustomizable\", ... }` for tables whose `IsCustomizable.Value=false` (system-managed; you must surface as `DONE_WITH_CONCERNS`).\n- Returns `{ \"status\": 204, ... }` on successful update.\n- Handles 401 token refresh and 429 back-off automatically.\n\n**If the helper returns status 403 `PrivilegeCheckFailed`:** the user lacks \"Customize System\" privilege. Print the table name and which privilege is missing, then STOP.\n\n**If status 400 with `ChangeTrackingEnabled cannot be disabled`:** ignore — that path only triggers when going from true to false, which we never do.\n\nPrint `✓ \u003Ctable>` after each 204; print `↷ \u003Ctable> (already enabled)` for no-ops; print `⚠ \u003Ctable> (uncustomizable)` for skips.\n\n### Step 5 — Publish customizations (targeted PublishXml, with PublishAllXml fallback)\n\n**Print before starting:**\n> \"→ Publishing customizations (targeted PublishXml on the entities just edited)…\"\n\n**Use targeted `PublishXml`** scoped to the entities that were actually modified — avoids the org-wide rate-limit storms (`0x80071151` \"concurrent PublishAll already running\") observed on shared envs. Empirical 2026-05-25.\n\n```bash\ncd -- '\u003Cworking_dir>' || { echo \"BLOCKED: cannot enter working_dir\" >&2; exit 1; }\n# Build the \u003Centities> XML body from the list of tables modified in Step 4\nnode \"${PLUGIN_ROOT}\u002Fscripts\u002Fdataverse-request.js\" \"\u003CenvUrl>\" POST \\\n  \"PublishXml\" --tenant-id \"\u003CtenantId>\" --body '{\n    \"ParameterXml\": \"\u003Cimportexportxml>\u003Centities>\u003Centity>\u003Ctable>\u003C\u002Fentity>\u003C\u002Fentities>\u003C\u002Fimportexportxml>\"\n  }'\n```\n\nSubstitute `\u003Centity>...\u003C\u002Fentity>` lines for every table the helper PUT'd flags on in Step 4. Tables that were no-ops or uncustomizable are omitted.\n\n**On 204**: success — continue to Step 6.\n\n**On 429 \u002F 0x80071151 (\"concurrent publish already running\")**: back off automatically via `dataverse-request.js`'s retry logic. If still failing after 4 retries, return `DONE_WITH_CONCERNS: publish bottlenecked on shared env; metadata changes are committed but maker portal will not refresh until next publish`. The downstream skill (`\u002Fsetup-offline-profile`) can proceed — metadata-level writes are durable.\n\n**Fallback to `PublishAllXml`** only when the targeted call returns a non-rate-limit\nerror such as `0x80048d19` and the owner separately approves the broader publication.\nTable-only approval does not authorize publishing unrelated changes.\n\n```bash\ncd -- '\u003Cworking_dir>' || { echo \"BLOCKED: cannot enter working_dir\" >&2; exit 1; }\nnode \"${PLUGIN_ROOT}\u002Fscripts\u002Fdataverse-request.js\" \"\u003CenvUrl>\" POST \\\n  \"PublishAllXml\" --tenant-id \"\u003CtenantId>\" --body '{}'\n```\n\nSame timeout-but-success handling as `\u002Fsetup-offline-profile` Step 8: if the client times out but a follow-up GET on the table's EntityMetadata shows the flags are set, treat as success.\n\n### Step 6 — Verify\n\n**Print before starting:**\n> \"→ Re-querying EntityMetadata to confirm flags are set…\"\n\nRe-run the Step 3 query for each modified table. Assert `IsAvailableOffline=true` and `ChangeTrackingEnabled=true` on every changed row. If any disagree, BLOCKED — something rejected the PUT silently (extremely unlikely; usually an indication of a managed-solution layer that's masking the unmanaged change).\n\n### Step 7 — Summary\n\nPrint:\n\n```text\n✓ Offline prerequisites enabled on \u003CN> table(s):\n  - cr123_note    (IsAvailableOffline + ChangeTrackingEnabled set)\n  - cr123_visit   (ChangeTrackingEnabled set; IsAvailableOffline already on)\n\nSkipped (already enabled): contact\n\nNext: return to the current \u002Fsetup-offline-profile workflow.\n```\n\nUpdate `\u003Cworking_dir>\u002Fmemory-bank.md` under `## Offline profile` with the timestamp\nand verified table list. Return the results to the current owner; do not launch\nanother offline setup workflow.\n\n## Status code\n\nThe literal first line of the skill's response is one of:\n- `DONE` — all requested tables now have both flags set\n- `DONE_WITH_CONCERNS: \u003Clist>` — some tables skipped (uncustomizable, publish warning, etc.)\n- `NEEDS_CONTEXT: \u003Cmissing>` — couldn't resolve table list and user didn't provide\n- `BLOCKED: \u003Creason>` — auth failure, privilege check failed, or post-PUT verification disagreed\n","**Shared instructions: [shared-instructions.md](${PLUGIN_ROOT}\u002Fshared\u002Fshared-instructions.md)** — read first.\n\n**References:**\n\n- [offline-profile-schema.md](${PLUGIN_ROOT}\u002Fshared\u002Freferences\u002Foffline-profile-schema.md) — entity field map (`IsAvailableOffline`, `ChangeTrackingEnabled`)\n\n# Enable Tables Offline\n\nFlip `IsAvailableOffline=true` AND `ChangeTrackingEnabled=true` on the `EntityMetadata` of one or more Dataverse tables, then publish customizations. This is the prerequisite shown in Image 4 of the maker portal (\"Can be taken offline\" + \"Track changes\") — without both, a table CANNOT be added to a Mobile Offline Profile.\n\nSequential (Dataverse metadata lock) and idempotent: re-running on an already-enabled table is a no-op.\n\n## Invocation context and root binding\n\nThis internal helper is always a **child invocation**. Before any project read or\ncommand, execute [app-working-directory.md](${PLUGIN_ROOT}\u002Fshared\u002Freferences\u002Fapp-working-directory.md).\nRequire the owner's absolute `working_dir`; `--working-dir`, when supplied, must\nidentify that same native-canonical root. Missing, relative, or conflicting root\ncontext returns `NEEDS_CONTEXT` before project access; an inaccessible directory\nis `BLOCKED`. Never use the launch cwd or introduce another root resolver.\n\nReceive `MOBILE_APP_ORCHESTRATING=1`, `orchestrator: setup-offline-profile`,\n`working_dir`, `phase`, `approved_scope`, and supplied answers. Preserve the\nselected environment ID\u002FURL\u002Ftenant and exact table\u002Fprerequisite\u002Fpublication\nallowlist. The marker is not approval. Reuse only matching current offline\napproval; a missing or changed scope returns `NEEDS_CONTEXT` to the owner.\nFor `--plan-only` or a planning-phase handoff, return the proposed prerequisite\nchanges after permitted read-only inspection, before PUT, publication, or\nartifact writes. A gate response cannot lift proposal-only mode.\n\nApply the canonical root contract to **every shell call and file tool**.\nRe-supply the absolute `PLUGIN_ROOT` and invocation context on each call; no\nprior `cd`, export, or shell variable persists. Missing values return\n`NEEDS_CONTEXT`; never execute an unresolved placeholder.\nAll linked recovery commands, re-GET verification, and retries use the same\nroot, environment, and explicit tenant. Read only absolute app-local paths,\nincluding `\u003Cworking_dir>\u002Fpower.config.json`, `\u003Cworking_dir>\u002Fmemory-bank.md`,\nand the manifest locations below.\n\n## Workflow\n\n1. Verify project & auth → 2. Resolve table list → 3. Inspect current state → Gate → 4. PUT EntityMetadata per table → 5. Publish → 6. Verify → 7. Summary\n\n---\n\n### Step 1 — Verify project & auth\n\n```bash\ncd -- '\u003Cworking_dir>' || { echo \"BLOCKED: cannot enter working_dir\" >&2; exit 1; }\nif [ ! -f power.config.json ] || [ ! -f app.config.js ]; then\n  echo \"BLOCKED: working_dir is not an initialized app\" >&2\n  exit 1\nfi\n```\n\nRequire the app's `environmentId` to match the owner's selected environment\nbefore any discovery or mutation. Use this non-persisting lookup from the same root:\n\n```bash\ncd -- '\u003Cworking_dir>' || { echo \"BLOCKED: cannot enter working_dir\" >&2; exit 1; }\nenvironment_id=$(node -p \"require('.\u002Fpower.config.json').environmentId || ''\") || {\n  echo \"BLOCKED: unreadable power.config.json\" >&2; exit 1;\n}\nif [ -z \"$environment_id\" ] || [ \"$environment_id\" != \"\u003Cselected-environment-id>\" ]; then\n  echo \"NEEDS_CONTEXT: selected environment does not match working_dir\" >&2\n  exit 1\nfi\nnode \"${PLUGIN_ROOT}\u002Fscripts\u002Fresolve-environment.js\" \"$environment_id\" --no-cache --require-tenant\n```\n\nCapture the **Environment URL** and **Tenant ID** from the resolver for\n`\u003CenvUrl>` and `\u003CtenantId>`. Pass this tenant explicitly on every helper call\nand retry below; missing or conflicting tenant context is `NEEDS_CONTEXT`.\nRequire the ID, URL, and tenant to match the owner; never switch accounts or\nenvironments to recover. STOP if not authenticated.\n\n### Step 2 — Resolve table list\n\nUse only the exact table allowlist in the owner's `approved_scope`. The comma-\nor space-separated table list in `$ARGUMENTS` must match it; `--working-dir` is\nroot context, not a table name. Missing or conflicting table selection returns\n`NEEDS_CONTEXT`; an explicitly empty approved list is a verified no-op.\n\nInspect `\u003Cworking_dir>\u002F.datamodel-manifest.json`, or\n`\u003Cworking_dir>\u002Fdocs\u002Fplan-artifacts\u002F.datamodel-manifest.json` for newer apps, only\nto verify those selected tables. The manifest is not permission to enable every\nrow. Do not discover another app's manifest or expand the allowlist silently.\n\n### Step 3 — Inspect current state\n\n**Print before starting:**\n> \"→ Querying current IsAvailableOffline + ChangeTrackingEnabled for \u003CN> table(s)…\"\n\nFor each table, in sequence:\n\n```bash\ncd -- '\u003Cworking_dir>' || { echo \"BLOCKED: cannot enter working_dir\" >&2; exit 1; }\nnode \"${PLUGIN_ROOT}\u002Fscripts\u002Fdataverse-request.js\" \"\u003CenvUrl>\" GET \\\n  \"EntityDefinitions(LogicalName='\u003Ctable>')?\\$select=LogicalName,DisplayName,IsAvailableOffline,ChangeTrackingEnabled,IsCustomizable\" \\\n  --tenant-id \"\u003CtenantId>\"\n```\n\nBuild a status table:\n\n```text\n| Table              | IsAvailableOffline | ChangeTrackingEnabled | IsCustomizable | Needs change? |\n|--------------------|--------------------|-----------------------|----------------|---------------|\n| cr123_note         | false              | false                 | true           | YES (both)    |\n| cr123_visit        | true               | false                 | true           | YES (track)   |\n| contact            | true               | true                  | true           | NO            |\n```\n\n**Hard rule:** if `IsCustomizable.Value=false` on any table, that table CANNOT be modified. Drop it from the change set and flag in `DONE_WITH_CONCERNS` — system-managed tables (most OOB) require an admin solution patch path the skill does not handle.\n\n### Gate — Approval before mutation\n\nCompare the status table from Step 3 with the owner's approved prerequisite and\npublication delta. Matching current Gate 1 approval is reused without a duplicate\nprompt. Otherwise return the status table and `NEEDS_CONTEXT: offline prerequisite\napproval` to `\u002Fsetup-offline-profile`, which owns the approval gate. Do not widen\nscope or override proposal-only mode.\n\nPlan body:\n\n```text\nThe following EntityMetadata changes will be PUT in sequence:\n\ncr123_note   → set IsAvailableOffline=true, ChangeTrackingEnabled=true\ncr123_visit  → set ChangeTrackingEnabled=true (IsAvailableOffline already true)\n\nAfter all updates, targeted PublishXml will publish only the changed tables.\n\nTables already in the desired state are skipped (no API call).\n```\n\nIf the user rejects, STOP. Proceed only with the exact approved delta.\n\n### Step 4 — PUT EntityMetadata per table\n\n**Print before starting:**\n> \"→ Updating EntityMetadata for \u003CN> table(s) sequentially (Dataverse serializes metadata writes)…\"\n\n> **⚠️ Concurrency rule — do not violate.** Metadata writes hold an exclusive lock per org. Issue one PUT, wait for 2xx, then the next. No batching, no parallel calls. Same rule as `\u002Fadd-dataverse` Step 5.\n\nFor each table needing change (skip ones already in target state):\n\n```bash\ncd -- '\u003Cworking_dir>' || { echo \"BLOCKED: cannot enter working_dir\" >&2; exit 1; }\nnode \"${PLUGIN_ROOT}\u002Fscripts\u002Fupdate-entity-offline-flags.js\" \"\u003CenvUrl>\" \\\n  --table \"\u003Ctable>\" \\\n  --offline true \\\n  --tracking true \\\n  --tenant-id \"\u003CtenantId>\"\n```\n\nThe helper:\n- Re-reads `EntityMetadata` to pick up the current `MetadataId` + `SchemaName` (both required in the PUT body — Dataverse rejects PUT without them).\n- Sends `MSCRM.MergeLabels: true` so display labels are preserved (the alternative wipes labels — never use `false`).\n- Returns `{ \"status\": 200, \"noop\": true, ... }` if the table is already in the target state (skip silently).\n- Returns `{ \"status\": 200, \"skipped\": \"uncustomizable\", ... }` for tables whose `IsCustomizable.Value=false` (system-managed; you must surface as `DONE_WITH_CONCERNS`).\n- Returns `{ \"status\": 204, ... }` on successful update.\n- Handles 401 token refresh and 429 back-off automatically.\n\n**If the helper returns status 403 `PrivilegeCheckFailed`:** the user lacks \"Customize System\" privilege. Print the table name and which privilege is missing, then STOP.\n\n**If status 400 with `ChangeTrackingEnabled cannot be disabled`:** ignore — that path only triggers when going from true to false, which we never do.\n\nPrint `✓ \u003Ctable>` after each 204; print `↷ \u003Ctable> (already enabled)` for no-ops; print `⚠ \u003Ctable> (uncustomizable)` for skips.\n\n### Step 5 — Publish customizations (targeted PublishXml, with PublishAllXml fallback)\n\n**Print before starting:**\n> \"→ Publishing customizations (targeted PublishXml on the entities just edited)…\"\n\n**Use targeted `PublishXml`** scoped to the entities that were actually modified — avoids the org-wide rate-limit storms (`0x80071151` \"concurrent PublishAll already running\") observed on shared envs. Empirical 2026-05-25.\n\n```bash\ncd -- '\u003Cworking_dir>' || { echo \"BLOCKED: cannot enter working_dir\" >&2; exit 1; }\n# Build the \u003Centities> XML body from the list of tables modified in Step 4\nnode \"${PLUGIN_ROOT}\u002Fscripts\u002Fdataverse-request.js\" \"\u003CenvUrl>\" POST \\\n  \"PublishXml\" --tenant-id \"\u003CtenantId>\" --body '{\n    \"ParameterXml\": \"\u003Cimportexportxml>\u003Centities>\u003Centity>\u003Ctable>\u003C\u002Fentity>\u003C\u002Fentities>\u003C\u002Fimportexportxml>\"\n  }'\n```\n\nSubstitute `\u003Centity>...\u003C\u002Fentity>` lines for every table the helper PUT'd flags on in Step 4. Tables that were no-ops or uncustomizable are omitted.\n\n**On 204**: success — continue to Step 6.\n\n**On 429 \u002F 0x80071151 (\"concurrent publish already running\")**: back off automatically via `dataverse-request.js`'s retry logic. If still failing after 4 retries, return `DONE_WITH_CONCERNS: publish bottlenecked on shared env; metadata changes are committed but maker portal will not refresh until next publish`. The downstream skill (`\u002Fsetup-offline-profile`) can proceed — metadata-level writes are durable.\n\n**Fallback to `PublishAllXml`** only when the targeted call returns a non-rate-limit\nerror such as `0x80048d19` and the owner separately approves the broader publication.\nTable-only approval does not authorize publishing unrelated changes.\n\n```bash\ncd -- '\u003Cworking_dir>' || { echo \"BLOCKED: cannot enter working_dir\" >&2; exit 1; }\nnode \"${PLUGIN_ROOT}\u002Fscripts\u002Fdataverse-request.js\" \"\u003CenvUrl>\" POST \\\n  \"PublishAllXml\" --tenant-id \"\u003CtenantId>\" --body '{}'\n```\n\nSame timeout-but-success handling as `\u002Fsetup-offline-profile` Step 8: if the client times out but a follow-up GET on the table's EntityMetadata shows the flags are set, treat as success.\n\n### Step 6 — Verify\n\n**Print before starting:**\n> \"→ Re-querying EntityMetadata to confirm flags are set…\"\n\nRe-run the Step 3 query for each modified table. Assert `IsAvailableOffline=true` and `ChangeTrackingEnabled=true` on every changed row. If any disagree, BLOCKED — something rejected the PUT silently (extremely unlikely; usually an indication of a managed-solution layer that's masking the unmanaged change).\n\n### Step 7 — Summary\n\nPrint:\n\n```text\n✓ Offline prerequisites enabled on \u003CN> table(s):\n  - cr123_note    (IsAvailableOffline + ChangeTrackingEnabled set)\n  - cr123_visit   (ChangeTrackingEnabled set; IsAvailableOffline already on)\n\nSkipped (already enabled): contact\n\nNext: return to the current \u002Fsetup-offline-profile workflow.\n```\n\nUpdate `\u003Cworking_dir>\u002Fmemory-bank.md` under `## Offline profile` with the timestamp\nand verified table list. Return the results to the current owner; do not launch\nanother offline setup workflow.\n\n## Status code\n\nThe literal first line of the skill's response is one of:\n- `DONE` — all requested tables now have both flags set\n- `DONE_WITH_CONCERNS: \u003Clist>` — some tables skipped (uncustomizable, publish warning, etc.)\n- `NEEDS_CONTEXT: \u003Cmissing>` — couldn't resolve table list and user didn't provide\n- `BLOCKED: \u003Creason>` — auth failure, privilege check failed, or post-PUT verification disagreed\n",{"name":5,"model":25,"description":7,"allowed-tools":44,"user-invocable":40,"disable-model-invocation":45},"Read, Edit, Write, Grep, Glob, Bash, AskUserQuestion, EnterPlanMode, ExitPlanMode",true,"main","0a55a88fa2855404029d1e5450faf92878baf763","plugins\u002Fmobile-apps\u002Fskills\u002Fenable-tables-offline",232,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills","https:\u002F\u002Fmicrosoft.github.io\u002Fpower-platform-skills\u002F","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-14 21:46:39",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":45},[58,61,64],{"tool":59,"command":60},"npx","npx skills add microsoft\u002Fpower-platform-skills --skill enable-tables-offline",{"tool":62,"command":63},"bunx","bunx skills add microsoft\u002Fpower-platform-skills --skill enable-tables-offline",{"tool":65,"command":66},"pnpm","pnpm dlx skills add microsoft\u002Fpower-platform-skills --skill enable-tables-offline","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fmobile-apps\u002Fskills\u002Fenable-tables-offline\u002FSKILL.md",[69,75,81],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"assets\u002Fadr_template.md","ASSET","资产文件",6950,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fdot_claude\u002Fskills\u002Fiot-system-architect\u002Fassets\u002Fadr_template.md",{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fargus_architecture.md","REFERENCE","参考文档",13366,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fdot_claude\u002Fskills\u002Fiot-system-architect\u002Freferences\u002Fargus_architecture.md",{"path":82,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fdesign_patterns.md",16732,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fdot_claude\u002Fskills\u002Fiot-system-architect\u002Freferences\u002Fdesign_patterns.md",[86,94,113,135,153,167],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":93},"01M78JN2BFRRV1J54Q6WKZQ08D","compare-site-configurations","Compare Power Pages site configurations between two environments, such as dev, test and production, or between a local download and the live site, and explain which differences change site behavior. Use when a site works in one environment but not another (for example, works in dev but fails in test), to check configuration drift before promoting or deploying, or to see what changed between two sites. Produces a shareable HTML report and a JSON file that VS Code can import.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fpower-pages\u002Fskills\u002Fcompare-site-configurations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":95,"name":37,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":39},"01M699WVHX0XN59EPBTTPEKYPG","Use when Process Intelligence needs building, explicit cloud\u002Faccount\u002Fenvironment configuration, sign-in, connection diagnostics, or recovery from an authentication error.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprocess-intelligence\u002Fskills\u002Fsetup\u002FSKILL.md",[],[37,100,101,102,103,104,105,106,107,108,36,109,110,111,33,112],"configuration","diagnostics","error","environment","cloud","when","connection","authentication","use","recovery","process","sign","intelligence",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":124,"publishedAt":39},"01M699WSR9EX55YY1WD9J22FEG","report-issue","Use when the user wants a Process Intelligence bug-report draft or support summary for a failed operation.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprocess-intelligence\u002Fskills\u002Freport-issue\u002FSKILL.md",[119],{"categoryNo":120,"categoryName":121,"taxonomyType":122,"taxonomyTypeDesc":123},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[125,126,127,128,108,105,129,130,110,131,112,132,133,23,134],"issue","report","report issue","bug-report","operation","draft","bug","summary","user","support",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":39},"01M699WR26YQ9Q21KE6MJF5B2G","investigate-process","Use when a broad Process Mining business question, observed pattern or competing explanation needs investigation across analytical perspectives.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprocess-intelligence\u002Fskills\u002Finvestigate-process\u002FSKILL.md",[],[142,110,143,144,108,145,146,105,147,148,149,33,150,151,152],"investigate","investigate process","question","process mining","business","across","perspectives","mining","pattern","investigation","analytical",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":159,"publishedAt":39},"01M699WP9SDG5ZR12P8VYNXKTN","derive-metric","Use when a requested measure is missing, a saved custom metric needs reuse, or an ephemeral formula or derived scalar is needed.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprocess-intelligence\u002Fskills\u002Fderive-metric\u002FSKILL.md",[],[160,161,162,163,164,165,108,105,166,33],"metric","derive metric","missing","formula","custom","reuse","saved",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":173,"publishedAt":39},"01M699WMG5R8P6SMTDAS1TKF9E","compare-cohorts","Use when comparing process cohorts, departments, periods or before-and-after results under matched definitions.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprocess-intelligence\u002Fskills\u002Fcompare-cohorts\u002FSKILL.md",[],[174,175,108,105,176,110,33],"compare","compare cohorts","results"]