PranavNagrecha/AwesomeSalesforceSkills / skills/admin/dynamic-forms-migration
dynamic-forms-migration
VerifiedMigrating standard Lightning Record Page layouts (Page Layouts on the Record Detail component) to Dynamic Forms — converting fields and sections to component-level placement, replacing record-type-driven layouts with field-visibility filters, retaining or replacing Quick Action layouts, planning custom-object vs standard-object rollout, and verifying field-level security and Reading View parity. NOT for Dynamic Forms initial setup (use admin/dynamic-forms-and-actions) or Lightning Record Page design from scratch (use admin/lightning-app-builder-advanced).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 21.1 KB |
| references/examples.md | markdown | 8.0 KB |
| references/gotchas.md | markdown | 6.9 KB |
| references/llm-anti-patterns.md | markdown | 6.5 KB |
| references/well-architected.md | markdown | 6.6 KB |
| scripts/check_dynamic_forms_migration.py | script | 3.2 KB |
| templates/dynamic-forms-migration-template.md | markdown | 3.0 KB |
scripts/check_dynamic_forms_migration.py
View on GitHub#!/usr/bin/env python3
"""Checker script for Dynamic Forms Migration skill.
Scans FlexiPage XML files for common migration concerns:
- Field components marked `isRequired=true` AND with a `<visibilityRule>` (save-failure trap)
- Visibility rules using `$User.Profile.Name` (brittle; recommend Custom Permission)
- Field components without any sectional grouping (organizational smell)
Stdlib only.
Usage:
python3 check_dynamic_forms_migration.py --project-dir path/to/project
"""
from __future__ import annotations
import argparse
import re
import sys
from pathlib import Path
def parse_args() -> argparse.Namespace:
p = argparse.ArgumentParser(description=__doc__, formatter_class=argparse.RawDescriptionHelpFormatter)
p.add_argument("--project-dir", type=Path, default=Path.cwd())
p.add_argument("--strict", action="store_true")
return p.parse_args()
def find_flexipages(root: Path) -> list[Path]:
return [p for p in root.rglob("*.flexipage-meta.xml") if p.is_file() and ".sfdx" not in p.parts]
def scan(root: Path) -> list[tuple[str, Path, int, str]]:
findings: list[tuple[str, Path, int, str]] = []
for f in find_flexipages(root):
try:
text = f.read_text(encoding="utf-8", errors="ignore")
except OSError:
continue
# Find each fieldInstance block and check for required + visibility combo
for match in re.finditer(r'<fieldInstance>(.*?)</fieldInstance>', text, flags=re.DOTALL):
block = match.group(1)
if '<isRequired>true</isRequired>' in block and '<visibilityRule>' in block:
line_no = text[:match.start()].count('\n') + 1
# Try to extract the field name for the message
fld = re.search(r'<fieldItem>([^<]+)</fieldItem>', block)
name = fld.group(1) if fld else "(unknown)"
findings.append(("required-and-hidden", f, line_no,
f"Field {name} is both required AND has a visibilityRule — save will fail when hidden"))
# Profile name visibility rules
for line_no, line in enumerate(text.splitlines(), start=1):
if '$User.Profile.Name' in line:
findings.append(("profile-string", f, line_no,
"Visibility rule uses $User.Profile.Name (brittle to renames) — prefer $Permission.<CustomPermissionName>"))
return findings
def main() -> int:
args = parse_args()
root = args.project_dir.resolve()
if not root.exists():
print(f"ERROR: project dir not found: {root}", file=sys.stderr)
return 2
findings = scan(root)
print(f"Scanned: {root}")
print(f"Findings: {len(findings)}")
by_cat: dict[str, list] = {}
for cat, f, ln, msg in findings:
by_cat.setdefault(cat, []).append((f, ln, msg))
for cat in sorted(by_cat):
print(f"\n=== {cat} ({len(by_cat[cat])}) ===")
for f, ln, msg in by_cat[cat][:50]:
rel = f.relative_to(root) if f.is_relative_to(root) else f
print(f" {rel}:{ln} — {msg}")
if len(by_cat[cat]) > 50:
print(f" ... and {len(by_cat[cat]) - 50} more")
return 1 if (args.strict and findings) else 0
if __name__ == "__main__":
sys.exit(main())
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |