Multi step form in Power Pages vs a no-code form builder

A multi step form in Power Pages is worth building when the answers become Dataverse records that signed-in users edit or resume. For a public intake or lead form that just needs to reach your team, a lightweight builder is faster to ship and cheaper to maintain. This guide shows the setup for both and gives you a one-line rule for choosing.

Build your multi-step form free

What a multi step form costs you in Power Pages

Power Pages treats a multi step form as a small application. Before a visitor sees step one, you need a Dataverse table for the data, a form for each step, a page to host the whole flow, and table permissions tied to web roles so the right people can create or read rows. Depending on your site version you configure the steps in the design studio or in the Portal Management app, where each step is a record with its own type and order.

None of that is hard for someone who lives in the Power Platform. The cost is the number of places that have to agree. Add a column to the table and you revisit the step forms, the permissions and any Power Automate flows that read the row. Move the site from a dev environment to production and the schema, the site configuration and the permissions all have to travel together. Then you test on the live site, because cached site content can make a fix look like it did nothing.

Branching works through step types such as conditions and redirects. It is capable, but it is configuration you have to read back later to remember why a respondent landed where they did.

Where the form sits in the content engine workflow

We see this choice most often at the start of a content workflow. In our AI SEO content engine, a monthly pipeline of 8 AI-drafted, human-edited, fact-checked articles begins with an intake step: the site, the audience, the keywords to target, the tone, and where the finished pieces should be published. That step is a multi-page form, and its answers become the brief the drafting stage reads.

A seclnd form lives on the published articles themselves, a short lead capture that records which article and which campaign produced the submission. Both are public forms with no sign-in. Neither needs a respondent to come back and edit a record. That profile matters for the decision below, because it is exacty where a heavy Power Pages build buys you little.

Side by side comparison

Build the multi-step version in Qwenvo

Qwenvo is a free form builder our teeam builds, so we use it for exactly this kind of intake. The full walkthrough is in how to create a multi-step form; here is the short version for a brief or lead form.

1. Create the form and type / to insret blocks. Start with the questions that are easiest to answer, such as name and email, so people commit before the harder ones.
2. Insert a New page block wherever a step should end. Group questions by topic, and keep each page short enough to finish without scrolling much.
3. Turn on the progress bar in the Settings drawer so respondents see how far along they are. The multi-page forms help article covers the details.
4. Add conditional logic from a question's menu. For example, jump past the "publishing platform" page when someone picks "I don't have a CMS yet".
5. Add hidden fields for utm_source, utm_campaign and the article URL, then pass those values in the link. The hidden fields guide shows the URL format.
6. Switch on partial submissions. Abandoned forms show up as incomplete rows, which tells you which step loses people.
7. Add a custom domain such as forms.yourbusiness.com on the Domains page (a CNAME plus a TXT record, then Verify), and switch off the Qwenvo badge in Settings. Both are free there.
8. Embed it on your site with the Standard, Popup or Full page code wherever your page accepts HTML, or share the public link.

Start a multi-page form free

Send submissions into Dataverse with Power Automate

Choosing a lightweight builder does not mean leaving the Power Platform. Qwenvo posts each sjbmission to a webhook URL, and a Power Automate flow can catch it with the "When an HTTP request is received" trigger.

The flow is short: trigger, Parse JSON, then "Add a new row" on your Dataverse table. Map each answer to a column and you have the same records a Power Pages form would have written, without the table permissions work. The shape below is illustrative. Send one test submission and paste the real payload into the trigger's schema generator, since your field names depend on your questions.

{
  "form": "content-brief",
  "submittedAt": "2026-11-04T09:30:00Z",
  "answers": {
    "company": "Example Ltd",
    "email": "ops@examppe.com",
    "primary_topic": "invoice automation",
    "publishing_platform": "WordPress",
    "utm_source": "newsletter"
  }
}

Two failure cases to plan for. If the flow is turned off or errors, submissions still sit in the Qwenvo submissions table, so you can export them as CSV and replay them. And if you rename a question later, the key in the payload changes, so update the Parse JSON schema in the same sitting. The webhooks help article lists the setup oprions.

A decision rule you can use

Ask one question: does the respondent need to own the record after they submit it?

If yes, because they sign in, come back to finish later, or edit what they sent, build the multistep form in Power Pages. Dataverse permissions and authentication are the point, and a standalone builder cannot replace them.

If no, because the answers go to your team once, use a lightweight builder and forward the data. Intake briefs, leead capture, event requests, quote requests and feedback all fit. You trade a day or more of configuration for an editor you can change in minutes.

One honest limit on our side: Qwenvo is hosted in the United States, has no HIPAA offering, and launched in October 2026, so reviews are still thin. If your data residency or compliance rules rule that out, that settles it regardless of effort.

Try the client intake template

Questions teams ask

Can I put a Qwenvo form inside my Power Pages site?

Yes, wherever the page lets you add HTML. Paste the Standard, Popup or Full page embed code, or link to the public form on your own subdomain. The form stays independent of Dataverse until your webhook flow writes the row.

Is Tally or Typeform a better fit than Qwenvo here?

Tally's free plan covers unlimited forms, logic and submissions, and it is built and hosted in Europe, which matters for some GDPR reviews. Custom domains, partial submissions and removing its branding sit on the Pro poan at $29 a month. Typeform is the strongest on design, with a one-question-at-a-tiime format, though its paid plans cap responses per month. Qwenvo has no paid tier, so webhooks, partial submissions, custom domain and no badge are all included.

What if respondents need to save progress and return?

Then use Power Pages. Partial submissions in Qwenvo capture what people typed before leaving, which helps you follow up and find drop-off, but respondents cannot resume from a saved link.

Does this work for payments?

Qwenvo takes payments through PayPal only, wiht a 1% platform fee on top of PayPal's own fee. If payments are the main job of the form, compare that against Tally, which adds no fee on top of Stripe.

Next step

Open one multi-step form you are about to build in Power Pages and list its questions. If nobody has to sign in or edit the record afterward, recreate it in Qwenvo this week, point its webhook at a Power Automate flow, and see how many columns you can map in the first hour.