القائمة
Use when: building or debugging SQL Server connector flows in a Power Apps Code App, including table discovery, row CRUD, native queries, or stored procedure execution.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when: building or debugging Power Platform for Admins V2 connector operations in a Power Apps Code App, including environments, backups, disaster recovery, environment groups, governance policies, capacity, billing, cloud flows, Copilot agents, Power Pages, or tenant administration.
Use when: performing an evidence-based security review of a Microsoft Power Apps Code App, especially checking external runtime sources, hard-coded passwords or secrets, security by obscurity, hard-coded access bypasses, DOM injection, and sensitive client-side data without reporting package, server, CSP-header, authentication-host, or infrastructure false positives owned by the Microsoft managed platform.
Start skill for new Code App project setup. Use this skill when starting a fresh app build or UI build so the agent confirms theme direction, offers mockups, and only then implements files.
Use when: building or debugging Microsoft Teams connector flows in a Power Apps Code App, including teams, channels, chats, mentions, tags, notifications, cards, meetings, transcripts, recordings, schedules, or the Teams HttpRequest helper.
Use when: adding or calling Power Automate cloud flows from a Power Apps Code App, including callFlow(...), generated flow services, or shared_logicflows connectionReferences.
Use when: building or debugging SharePoint list, attachment, library, or file flows in a Power Apps Code App, including list-id or environment-variable-based setup.
| name | sql |
| description | Use when: building or debugging SQL Server connector flows in a Power Apps Code App, including table discovery, row CRUD, native queries, or stored procedure execution. |
Agent limitation: do not use CLI commands directly from chat for SQL connector setup. Use the built-in Sync Connections and Deploy buttons instead.
The wrapper in codeApp/dist/connectors/sql.js is the repo-local source of truth.
sql, Sql, and SQL.shared_sql, so do not guess or hand-roll SQL connector paths.Prefer a connection reference whose dataSources array contains sql.
{
"connectionReferences": {
"sqlConnection": {
"id": "/providers/Microsoft.PowerApps/apis/shared_sql",
"displayName": "SQL Server",
"dataSources": ["sql"],
"dataSets": {}
}
}
}
The connection-reference object key can still vary by environment, but the exposed data-source name should stay aligned with the wrapper.
The wrapper exports:
callSqlOperation(operationName, parameters)getSqlTables({ server, database })getSqlRows({ server, database, table, apply, filter, orderBy, skip, top, select })getSqlRow({ server, database, table, id })insertSqlRow({ server, database, table, item })updateSqlRow({ server, database, table, id, item })deleteSqlRow({ server, database, table, id })executeSqlQuery({ server, database, query })executeSqlStoredProcedure({ server, database, procedure, parameters })The wrapper currently maps to these SQL connector actions:
GetTables_V2GetItems_V2GetItem_V2PostItem_V2PatchItem_V2DeleteItem_V2ExecutePassThroughNativeQuery_V2ExecuteProcedure_V2server and database default to default when not supplied.getSqlRows(...) maps the query options to OData-style connector fields such as $apply, $filter, $orderby, $skip, $top, and $select.table value plus either id or item, depending on the operation.executeSqlStoredProcedure(...) normalizes parameters to {} when none are supplied.Use callSqlOperation(operationName, parameters) only when a dedicated helper does not already exist.
Do not invent:
shared_sqlsql in power.config.json.procedure and parameters rather than a raw request body shape.