Ravindra

Find The Unmatched and Match Records in 2 Array  by using power Automate  Create Different Types of Joint In Power Automate 1. Challenge: Handling and comparing two arrays based on a unique column in Power Automate without using the 'Apply to Each' action. 2. Objective: Find matching and non-matching records across two arrays. 3. Goal: Perform various types of joins on the arrays, including inner join, outer join, union, and others, using this approach. For More info 👇 https://youtu.be/s-cySUJixfI video ✨ Thanks for reading! ✨ I hope you found this blog on the Microsoft Power Platform helpful! From Power Apps, Power Automate (Cloud & Desktop), Canvas Apps, Model-driven Apps, Power BI, Power Pages, SharePoint, Dynamics 365 (D365), Azure, and more, I cover a wide range of topics to help you harness these powerful tools. Don’t miss out on future tips, tutorials, and insights—hit that subscribe button to get the latest posts right to your inbox. 💌 💬 I’d love to h

 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

  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

 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