Setting the scope of a Business Rule to 'Entity' ensures that the logic executes server-side. This means the rule will enforce the logic across all model-driven app forms, canvas apps, and programmatic updates (like Power Automate, API calls, or bulk data imports). 'All Forms' only applies the logic client-side across all model-driven UI forms, meaning an API update would bypass the rule.

Power Automate cloud flows are the premier orchestration tool for cross-system and cross-service automation. While Business Rules and classic workflows handle Dataverse-specific data operations natively, sending mobile push notifications (via the Power Apps Notification connector) and posting Adaptive Cards to Microsoft Teams require interacting with external APIs and services. Only Power Automate provides the massive connector ecosystem required to seamlessly orchestrate this cross-platform scenario.

To integrate a custom Copilot Studio agent into a Canvas app, you use the native Copilot control. Once added to the screen, you navigate to the properties pane of the control. Under the data source or 'Copilot' property, you can browse and select any Copilot Studio agent that has been created and published within the same environment. Using an iFrame (Option 3) is a legacy workaround for web pages, not the native, integrated Canvas app experience.

For end-users in Model-driven apps, the Copilot sidecar provides powerful data interaction capabilities. Users can ask Copilot to summarize the key points of the record they currently have open (Option 1). They can also interact with views/grids by asking natural language questions to filter data, find specific records, or calculate quick aggregations based on the data visible to them (Option 3). Modifying form layouts (Option 2) or generating code/plugins (Option 4) are maker-level capabilities, not end-user features.

Formula columns are the modern, Microsoft-recommended approach for real-time, record-level calculations in Dataverse, replacing legacy Calculated columns. They natively use standard Power Fx syntax and offer far better integration across the Power Platform, including vastly improved delegation support when queried and filtered from within Canvas apps. Rollup columns are asynchronous and used for aggregating related 1:N records.

The 'Filter rows' property in Dataverse actions (and many other REST APIs) uses standard OData query syntax. In OData, mathematical comparison operators like `=`, `<`, or `>` are invalid. You must use OData logical operators such as `eq` (equals), `ne` (not equals), `lt` (less than), and `gt` (greater than). The query `name = 'Contoso'` is invalid syntax and must be written as `name eq 'Contoso'`.

The 'Temperature' setting controls the randomness and creativity of the AI model's responses. A higher temperature (closer to 1) results in more diverse, creative, and potentially unpredictable outputs (hallucinations). Decreasing the temperature (closer to 0) makes the model's responses more deterministic, focused, and factual, which is ideal for strict translation or summarization tasks where imagination is not desired.

The AI Builder Object Detector control returns its analysis in a specific table property named `VisionObjects`. This table contains a row for every individual object the AI identified in the image, along with its label and confidence score. To get the total number of items detected, you must use the `CountRows()` function against this specific `VisionObjects` property. Options containing `.Results` or `.ObjectCount` use incorrect property names for this specific control.

To create dynamic placeholders in a custom prompt in AI Hub, you must explicitly use the 'Add input variable' button/menu in the designer. This creates the variable and allows you to insert its dynamic token into the prompt text. You must then provide 'Sample data' for these variables to test the prompt. The AI Hub UI requires explicitly defining the input variables via its interface rather than relying solely on text-based curly brace syntax.

Within the modern Power Automate cloud flow designer, Copilot serves as an interactive development assistant. One of its primary capabilities is the 'Explain' feature. By selecting an action, scope, or the entire flow, a maker can ask Copilot to explain what the logic is doing. Copilot analyzes the actions, expressions, and parameters, and provides a clear, natural language summary of the execution flow, drastically reducing the time required to understand undocumented legacy automations.