Skip to main content
Promptivo logoPromptivo
Build a prompt

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.

Open in the builder →

Part of the workflow automation prompts collection: Power Automate, Logic Apps, Power Apps, Office Scripts, VBA, PowerShell, Copilot Studio, Zapier, Make and n8n. Writing your own? Read the automation prompt guide.

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
Work the problem internally, then give only the result. Do not narrate your reasoning unless it is part of the deliverable.

- 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.
- Follow the requested format exactly. Default to clean markdown. Be concise — no filler, no restating the question.
- Deliver the single best answer rather than hedging across several.
- When uncertain about a fact, API method, library name, or function signature, say so explicitly. Do not produce a plausible guess.
- Do not invent citations, URLs, or package names. If you don't know one, omit it or flag that you don't.
- 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

Tuned for your model

Get a version optimized for the AI you actually use:

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.

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.

Related prompts