Ravindra

 Create Solution Plan with Copilot   Start with a Plan Great solutions don’t begin with coding or designing the UI but by understanding the problem and user requirements. Power Apps Studio now offers tools to plan solutions right from the start. Developers can discuss the business problem with Copilot, ensuring the solution aligns with business needs. Users can describe their problem, share diagrams, and legacy app screenshots to draft user roles and requirements, which can be further refined with Copilot's help. Once requirements are clear, Power Apps will propose a data model, displayed as an entity relationship diagram (ERD). Makers can explore and update it visually. The system will also recommend the types of apps and automation (Canvas apps, model-driven apps, and cloud flows) that best fit the requirements. This process is collaborative and iterative—users can make changes to roles, data models, and user experiences at any point. The plan stays with the app, maki

  Public Preview of Column-Level Security for Masking Sensitive Data Data Masking in Customer Interactions: Key Points Overview : Data masking (also known as de-identification or obfuscation) protects sensitive information by replacing it with masked strings. This ensures that only authorized users can view the original data, while unauthorized users see the masked version. Purpose : Helps prevent exposure of sensitive information such as credit card numbers and social security numbers during customer interactions. Preview Feature : This is a preview feature, meaning it is available for early access and feedback but isn't intended for production use. May have restricted functionality compared to the final release. How Masking Works : Masking Rules : Define how data should be masked using regular expressions to identify patterns like credit card numbers or email addresses. Rules Setup : Create a solution in Power Apps. Add components and select "Secured masking rule" from

 Power Platform Admin Center AI prompts settings are now available in the Power Platform admin center (PPAC). Note: This image is AI-generated. Administrators can manage the availability of AI prompts in Power Platform and Copilot Studio for specific environments through PPAC. To access this feature setting, follow these steps in PPAC: Select Environments . Choose your environment. Navigate to Settings . Go to Product . Select Features . Adjust the AI prompts setting as needed. By default, this setting is set to "On." If the Copilot environment setting was previously set to "Off," the AI prompts setting will automatically match that value. Please note that if AI prompts have been disabled at the tenant level by your tenant admin, this setting will not be applied. AI prompts, which were previously managed through the Copilot settings, will now be controlled through the AI prompts setting in PPAC. If you want to disable AI prompts across your entire tenant, you can c

  Power Apps Cards vs. Adaptive Cards: When to Choose Which In the evolving landscape of Microsoft Power Platform and broader Microsoft 365 suite, understanding the tools at your disposal is crucial for optimizing your workflows and user experiences. Two notable components in this ecosystem are Power Apps Cards and Adaptive Cards . While both serve to enhance user interactions and streamline processes, they cater to different needs and scenarios. Power Apps Cards are designed for creating dynamic, task-oriented micro-applications that integrate seamlessly with Microsoft Power Platform tools, offering a low-code solution for building interactive and actionable business processes. They are ideal for scenarios requiring complex integrations, automated workflows, and user-centric task execution. On the other hand, Adaptive Cards provide a versatile, platform-agnostic way to present information and collect user input across various Microsoft 365 applications. Their JSON-based structure a

 Delay Until Action In Power Automate Delay Until By Using Schedule  Delay an action until a specific event occurs. You can use this action from the Microsoft Dataverse connector or any other connector as a step in the middle of the flow to delay subsequent steps until a specific event occurs. For example, you can define a flow that’s similar to the one in the following image to check for updates to  Account  rows in Dataverse, and then waits for an email confirmation from the  Account  manager before updating the change. Wait condition using delay until Use an OData-style time stamp in the  Delay until  property to delay the flow trigger until a specific UTC time. The key benefit of using the Dataverse  Delay until  property instead of the standard  Delay until   action  is the Dataverse  Delay until  property never expires, allowing the flow run to wait for long periods of time. Feature Delay Until Condition (Dataverse) Scheduled Delay Action Purpose Pauses the flow until a specific

 Documentation Updates Form Microsoft For  D365 & Power Platform Developers Source August 2024 Features Updates Developer System requirements, limits, and configuration values for Power Apps Improve solution performance, stability and reliability Define and query hierarchically related data Work with formula columns Low-code plug-ins Power Fx (preview) Visualize hierarchical data with model-driven apps Using Power Fx with commands Dataverse long term data retention overview FAQ for Copilot in model-driven apps Add Copilot for app users in model-driven apps Microsoft Dataverse documentation Create and use dataflows in Power Apps Import data from Excel and export data to CSV Importing and exporting data from Dataverse Sign in to Power Apps What are model-driven apps in Power Apps? Customize the command bar using command designer What is Power Apps? View table data in Power BI Desktop List of controls available for model-driven apps Create a solution Embed a Power BI report in a model

 Understand Solution and Layers In    In Solution, there are two distinct layer levels: Unmanaged layer . All imported unmanaged solutions and unmanaged customizations exist at this layer. The unmanaged layer is a single layer. Managed layers . All imported managed solutions and the system solution exist at this level. When multiple managed solutions are installed, the last one installed is above the managed solution installed previously. This means that the second solution installed can customize the one installed before it. When two managed solutions have conflicting definitions, the runtime behavior is either “Last one wins” or a merge logic is implemented. If you uninstall a managed solution, the managed solution below it takes effect. If you uninstall all managed solutions, the default behavior defined within the system solution is applied. At the base of the managed layers level is the system layer. The system layer contains the tables and components that are required for the pla

  The Copilot page (preview) is a centralized location in the Power Platform admin center for documents, insights, and controls relevant to Power Platform Copilots. Tenant admins can access educational resources about Copilot features, track usage, and access governance controls in one place by selecting Copilot in the navigation pane. Minimize image Edit image Delete image Usage The usage metrics in the Usage section show monthly active users for each Copilot feature. Active usage is defined as a session or interaction with Copilot. To learn more information on each feature, use the following links. The Copilot page is a place for Power Platform admins to go for information, visibility, and controls for Power Platform Copilots, including: Educational resources  to help you get started with Copilot, answer questions about data and security fundamentals for AI features, and stay up to date with new Copilot releases. Usage insights  to help you understand how many users are leveragin