Skip to content

Commit 3a5cd2e

Browse files
priyanshu92Copilot
andcommitted
address PR review feedback
- Normalize Web API site setting casing to Webapi/enableReadOperationPreview - Clarify that website-accesss reflects the current deployed code-site metadata folder Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
1 parent 7507f37 commit 3a5cd2e

3 files changed

Lines changed: 5 additions & 3 deletions

File tree

plugins/power-pages/skills/migrate-edm-to-spa/SKILL.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -597,7 +597,7 @@ When `.powerpages-site/` exists, translate EDM metadata into the hydrated SPA me
597597
| `webpagerule.yml` | `webpage-rules/<rule-name>.webpagerule.yml`, one file per rule |
598598
| `websitelanguage.yml` | `site-languages/<language-name>.websitelanguage.yml`, one file per language |
599599
| `publishingstate.yml` | `publishing-states/<state-name>.publishingstate.yml`, one file per state |
600-
| `websiteaccess.yml` | `website-accesss/<access-name>.websiteaccess.yml`, one file per access record |
600+
| `websiteaccess.yml` | `website-accesss/<access-name>.websiteaccess.yml`, one file per access record. `website-accesss` reflects the current deployed code-site folder name. |
601601
| `table-permissions/*.tablepermission.yml` | `table-permissions/*.tablepermission.yml` using SPA/code-site field names |
602602

603603
The field shape can also differ. EDM records often use `adx_`-prefixed keys such as `adx_name`, `adx_value`, and `adx_entitylogicalname`; code-site metadata commonly uses normalized keys such as `name`, `value`, and `entitylogicalname`. Use existing Power Pages scripts and skills when possible so IDs, filenames, field ordering, and normalized schemas are created correctly.

plugins/power-pages/skills/migrate-edm-to-spa/references/edm-to-spa-patterns.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -182,7 +182,7 @@ Classify site settings:
182182
| Authentication and registration | Auth plan and setup/admin tasks |
183183
| Profile redirects | SPA auth redirect handling and `/setup-auth` |
184184
| Web API settings | `/integrate-webapi` permissions/settings plan |
185-
| `WebAPI/enableReadOperationPreview` | Web API read behavior note; verify against current platform behavior before relying on it |
185+
| `Webapi/enableReadOperationPreview` | Web API read behavior note; verify against current platform behavior before relying on it |
186186
| Wildcard Web API fields (`Webapi/<table>/fields` = `*`) | High-risk access setting; review permissions carefully |
187187
| Search and facets | Search component, Web API/server logic, or manual gap |
188188
| Knowledge management | Usually manual or custom data implementation |

plugins/power-pages/skills/migrate-edm-to-spa/references/pac-edm-structure.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ Common target folders:
4141
| `server-logic/` | Server logic metadata when created through `/add-server-logic` |
4242
| `cloud-flow-consumer/` | Cloud flow consumer metadata when created through `/add-cloud-flow` |
4343
| `web-pages/`, `web-templates/`, `content-snippets/`, `page-templates/`, `web-files/` | Deployed code-site page/template/content/asset metadata |
44-
| `publishing-states/`, `site-languages/`, `sitemarkers/`, `weblink-sets/`, `webpage-rules/`, `website-accesss/` | Granular records that may correspond to EDM aggregate files |
44+
| `publishing-states/`, `site-languages/`, `sitemarkers/`, `weblink-sets/`, `webpage-rules/`, `website-accesss/` | Granular records that may correspond to EDM aggregate files. `website-accesss` reflects the current deployed code-site folder name. |
4545

4646
### Aggregate EDM to Granular SPA Translation
4747

@@ -59,6 +59,8 @@ Do not copy aggregate EDM files into `.powerpages-site/`. Translate records into
5959

6060
Field names can also differ. EDM often uses `adx_`-prefixed keys (`adx_name`, `adx_value`, `adx_entitylogicalname`), while code-site metadata commonly uses normalized keys (`name`, `value`, `entitylogicalname`). Prefer existing deterministic scripts and Power Pages skills to create target metadata instead of hand-writing converted YAML.
6161

62+
> Note: The SPA target folder for website access metadata is currently `website-accesss/` in deployed code-site metadata. Keep that spelling unless the deployed metadata format changes.
63+
6264
### FAQV2 Contrast Example
6365

6466
FAQV2 is a useful small EDM reference because it shows aggregate files that must become granular SPA metadata:

0 commit comments

Comments
 (0)