Focused styling workflow
- Create and configure the form in Dynamics, including its fields, validation, consent, and CAPTCHA.
- Copy the complete HTML from the form editor and describe the visual changes you want.
- Form Studio restyles the existing div-based form with scoped CSS, then compares the result with the supplied source.
- Review the returned full HTML and paste it into the same Dynamics form. Keep the original export as a backup.
- Save, run Check content, inspect the saved HTML and published result, and submit a real test inquiry.
What it preserves
The supplied form owns its fields and behaviour. Form Studio preserves generated IDs and classes, mapped and unmapped controls, target metadata, labels, required and validation settings, choices, hidden values, consent, CAPTCHA, original stylesheets, and scripts. New styling uses scoped CSS and div containers.
Table-based layouts need to be re-exported from Dynamics with the table-less layout enabled. Form Studio does not add or remove fields, change business logic, or take ownership of form layout.
Checks and limits
The source-comparison checker flags changed functional attributes, added or removed controls, generated copy changes, altered scripts or original stylesheets, layout tables, and common unscoped CSS. Browser checks are still needed for rendered geometry, cascade, accessibility, and validation display.
Regression fixtures and a local preview are not evidence of acceptance or submission processing in a Dynamics tenant. After pasting changes, inspect Designer output and verify a real submission in a safe test environment.
Spacing preset
Generated output uses a shared preset with 8px between labels and controls, 24px between fields and desktop columns, 10px between choices, and 12px between consent blocks. Form-scoped tokens can be adjusted for a requested design.