powerapps-sql
Skill1 starsChanged 12 days agoMITView on GitHub
Build the Power Apps orders canvas app backed by Azure SQL AdventureWorksLT. Use when working with examples/powerappssql, SalesLT order galleries, customer/product lookups, order-detail filtering, or the editable order form.
In this repository20 other files it gives its agents.
- nvidianimSkill
- zavahospitalSkill
- shift-handoffSkill
- adventureworksSkill
- auto-index-compactionSkill
- azure-sql-aiSkill
- debugging-sqlSkill
- inside-transaction-logSkill
- polybaseSkill
- secure-scalable-db-appSkill
- sql-by-exampleSkill
- sql-linuxSkill
- sqlserver2022Skill
- sqlserver2025Skill
- sql-versioning-appsSkill
- sql-versioningSkill
- tempdb-growthSkill
- waits-latches-spinlocksSkill
- waits-latches-spinlocks-workshopSkill
- wardgeneralSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Verify an Azure SQL database with the required SalesLT tables and access to a Power Platform environment.
- Distinctive: line 17
Follow the walkthrough to create the SQL connection and canvas app, then build the order gallery and customer-name lookup.
- Distinctive: line 19
Add the selected-order form, order-detail gallery, and product-name lookup.
- Distinctive: line 20
Verify actual control names before adapting formulas.
- Distinctive: line 22
Add sorting and save behavior.
- Distinctive: line 25
Do not delete shared connections, apps, or databases as automatic cleanup.
- Distinctive: line 27
Use synthetic sample orders and the repository publishing checks.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Power Apps with Azure SQL
Procedure
- Read the walkthrough.
Verify an Azure SQL database with the required
SalesLTtables and access to a Power Platform environment. - Confirm connection and authentication prerequisites. The inherited example uses SQL authentication; enter credentials only in the supported private connection UI, never in source or chat. Explain any firewall/authentication change and obtain approval before applying it.
- Follow the walkthrough to create the SQL connection and canvas app, then build the order gallery and customer-name lookup.
- Add the selected-order form, order-detail gallery, and product-name lookup. Verify actual control names before adapting formulas; template-generated names may differ from the walkthrough.
- Add sorting and save behavior. Test selection/context changes before writes. Obtain approval before updating order data, then verify the change in SQL.
- Save the app and report the tested behavior and remaining configuration. Do not delete shared connections, apps, or databases as automatic cleanup.
Use synthetic sample orders and the repository publishing checks.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

