Context-Aware Dataverse AI
Purpose
Design AI actions that understand the enterprise context around a Dataverse request before recommending or planning an operation.
Use this skill when the user needs:
- role-aware or department-aware action behavior
- permission-sensitive defaults
- relationship and dependency context
- business-rule-aware decision support
- localized or personalized Dataverse actions
- policy-aware recommendations
V1 Boundary
This skill creates context models and design guidance only. It does not read user profiles, permissions, Dataverse metadata, policies, or organizational data from a live tenant.
Workflow
- Identify the actor context: role, team, business unit, department, language, preferences, and operating channel.
- Identify the data context: tables, relationships, record ownership, lifecycle state, dependencies, and related processes.
- Identify the policy context: business rules, compliance constraints, approval rules, security policies, DLP constraints, and data sensitivity.
- Define context resolution order: explicit user input, current record or conversation context, known defaults, metadata, then clarification questions.
- Define personalization boundaries so convenience never bypasses permission, approval, audit, or policy checks.
Output Format
Return:
Context model: user, data, process, policy, and organizational context.Resolution strategy: where each context value should come from.Defaulting rules: safe defaults and when to ask the user.Permission-sensitive behavior: what changes by role or scope.Implementation guidance: Dataverse, Power Apps, and Power Automate areas to inspect or build.
1---2name: context-aware-dataverse-ai3description: Use when designing Dataverse AI behavior that adapts to user role, department, permissions, language, preferences, data context, relationships, business logic, policies, and organizational rules. Produces design guidance only and performs no live tenant inspection.4---56# Context-Aware Dataverse AI78## Purpose9Design AI actions that understand the enterprise context around a Dataverse request before recommending or planning an operation.1011Use this skill when the user needs:12- role-aware or department-aware action behavior13- permission-sensitive defaults14- relationship and dependency context15- business-rule-aware decision support16- localized or personalized Dataverse actions17- policy-aware recommendations1819## V1 Boundary20This skill creates context models and design guidance only. It does not read user profiles, permissions, Dataverse metadata, policies, or organizational data from a live tenant.2122## Workflow231. Identify the actor context: role, team, business unit, department, language, preferences, and operating channel.242. Identify the data context: tables, relationships, record ownership, lifecycle state, dependencies, and related processes.253. Identify the policy context: business rules, compliance constraints, approval rules, security policies, DLP constraints, and data sensitivity.264. Define context resolution order: explicit user input, current record or conversation context, known defaults, metadata, then clarification questions.275. Define personalization boundaries so convenience never bypasses permission, approval, audit, or policy checks.2829## Output Format30Return:31- `Context model`: user, data, process, policy, and organizational context.32- `Resolution strategy`: where each context value should come from.33- `Defaulting rules`: safe defaults and when to ask the user.34- `Permission-sensitive behavior`: what changes by role or scope.35- `Implementation guidance`: Dataverse, Power Apps, and Power Automate areas to inspect or build.36
rweisssieker-xp