Gemini prompt to build a Power Apps form with a submit flow
A prompt for a Power Apps form: the data source (SharePoint or Dataverse), the fields and validation, SubmitForm versus Patch, delegation-safe formulas in Power Fx, and the Power Automate flow triggered on submit.
Tuned for Gemini · structured role / context / task / output
Open in the builder →Ready-to-use prompt
# Role You are an experienced workflow-automation architect who designs reliable, maintainable automations on the platform in use: a precise trigger, exact connector and action names, explicit conditions, error handling, and a test plan. # Context Design a Power Apps form for equipment requests stored in a SharePoint list, with validation and a Power Automate flow that notifies IT on submit. # Task Design the automation described in the context above for the stated platform: the trigger, each action in order with exact connector or action names, the conditions and approvals, error handling and retries, and how to test it before it goes live. # How to approach this Be precise and literal about the requirements. Where a claim depends on facts, briefly note the reasoning or source behind it. - Lay the automation out in order: trigger, each action, the conditions and branches, error handling, then a test plan. Before you finalize, verify that the trigger fires on exactly the intended event and nothing else; every action names the real connector, action, or command for the stated platform; the first failure has a handling path: retry, notify, or stop; the test plan covers the main path and that first failure. # Constraints - Do not invent connector, action, or command names. If unsure one exists, say so and use the closest real alternative. - Prefer structured output — tables, numbered steps, or labeled sections — over long paragraphs where it aids clarity. - Flag anything in the context that is factually uncertain rather than asserting it confidently. - Cite a source only if you can identify it by full title (and year for papers). Never fabricate a URL. - Maintain consistent formatting across long outputs — if you start with H2 headings or bullets, don't drift to a different structure mid-document. - Deliver the result directly — no apologies or meta-commentary about the prompt itself. # Output format Return only the requested output. If multiple distinct variants would clearly help, label them (e.g., "Option A", "Option B"). # Done when - the output fully answers the goal in the Context section with no missing parts
Customize this prompt
Answer a few quick questions and Promptivo re-tunes the prompt above to your exact situation.
Start the interview →Why this prompt works
SharePoint and Dataverse behave differently in Power Apps and have different licensing. The prompt asks which one, since Dataverse needs a premium license.
Non-delegable formulas silently return partial data. The prompt asks the model to keep queries delegable and to name the limit.
Submit-then-notify is the common pattern. The prompt asks what the flow should do after submit and what the app shows on success and failure.
Using this prompt in Gemini
For power apps form, Gemini is a strong choice — it's especially good at concise, factual output and precise instruction-following. Promptivo formats this prompt the way Gemini works best: precise phrasing with brief reasoning cues where they improve accuracy.
Paste it into gemini.google.com, then replace any bracketed details with your own. Gemini is sensitive to wording, so this prompt pins down the exact terms and structure to keep the result from drifting.
Tuned for Gemini: how it differs
| Model | What Promptivo changes |
|---|---|
| ChatGPT | Concise instructions, strict format adherence, no preamble. |
| Claude | Explicit step-by-step thinking and clearly delimited output sections. |
| Gemini | Precise phrasing with brief reasoning cues where they improve accuracy. |
| Copilot | Office-ready output that pastes cleanly into Word, Outlook, and Excel, with tables and numbered steps. |
Questions, answered
- Should I use SubmitForm or Patch in Power Apps?
- SubmitForm for a standard edit form bound to a data source, Patch when you need to write specific fields, multiple records, or custom validation. The prompt asks which fits the form.
- What is the delegation limit in Power Apps?
- Non-delegable queries only process the first 500 records by default, up to 2,000 in settings. Use delegable functions and filters so the data source does the work.
- How do I run a flow when a Power Apps form is submitted?
- Add the flow with the PowerApps (V2) trigger, pass the fields as parameters, and call it in OnSuccess of the form or after Patch. The prompt designs both the app and the flow.
- Is Gemini good for power apps form?
- Yes. Gemini handles power apps form well thanks to its concise, factual output and precise instruction-following, and Promptivo tunes the prompt to match — precise phrasing with brief reasoning cues where they improve accuracy. Paste it into gemini.google.com.