What Is a Scorecard in Power BI? A Scorecard is a visual performance monitoring tool that allows you to track key metrics (goals) against predefined targets. Power BI’s Metrics (formerly Goals) feature helps you: Why Use Scorecards? Here’s why Scorecards are powerful for any team: Benefit Description Goal Alignment Track KPIs aligned to strategic objectives. Accountability Assign owners and collaborators for each goal. Real-time Tracking Monitor progress with live metrics. Visual Reporting Easy-to-read dashboards and history tracking. Step-by-Step: How to Build a Scorecard in Power BI Step 1: Navigate to Power BI Service Go to Power BI Service and choose the workspace where you want to create your Scorecard (Premium or Pro workspaces only). Step 2: Create a New Scorecard  You’ll now land on a blank Scorecard canvas. Step 3: Add Metrics to the Scorecard You can connect it to an existing Power BI dataset or manually input values. Step 4: Link Metrics to Data (Optional but Recommended) To automate tracking: This ensures your Scorecard updates automatically with data refreshes. Step 5: Customize the Scorecard You can also create hierarchies — group related goals under broader objectives. Step 6: Share & Collaborate Once your Scorecard is built: To conclude, Power BI Scorecards turn your data into action. They help track goals in real time, assign ownership, and keep teams focused on what matters most. Whether you’re managing a sales team, a project, or company-wide objectives — Power BI Scorecards are a game-changer for performance tracking. Want to bring visibility and accountability to your team goals? Head to Power BI Service and start building your first Scorecard today! Need help connecting metrics to your datasets? Reach out, and we’ll guide you step by step. We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfonts.com.

In today’s ever-evolving app development landscape, delivering an exceptional user experience is critical. Power Apps offers various tools to help developers create intuitive and efficient applications, and one of the standout features is the Form Component. This feature simplifies the design and usability of forms, making applications more scalable and maintainable. What Are Form Components? Form Components in Power Apps are modular elements that can be created once and reused across multiple forms or applications. By utilizing these components, developers can maintain consistency in design, functionality, and behavior. Essentially, they act as reusable building blocks for forms, streamlining the development process and enhancing the user experience. A common use case for Form Components is displaying entity-specific forms, such as a Quote Lookup field. Let’s explore how to implement a Form Component for this scenario. Implementing a Form Component for the Quote Lookup Field Imagine you have a requirement to display the form of a specific entity, such as a Quote, using the Quote Lookup field. Follow these steps to set it up: After selecting the form in the Component, the Lookup field will display like this Save and Publish: After adding the Form Component, click ‘Save’ and then ‘Publish’ to apply your changes. Key Considerations Once the setup is complete, your Quote Lookup field will display the desired form seamlessly. Here’s how it will look: With these steps, you can enhance the functionality of your forms and deliver a better user experience in your Dynamics 365 applications. Happy developing! We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfonts.com.

Introduction Document management is a critical aspect of any organization using Dynamics 365 CRM, and finding a simple, scalable solution can often be a challenge.  In this blog, I’ll show you how PowerApps Custom Pages can transform your document handling experience. By leveraging model-driven capabilities, I’ve built a solution from scratch that allows you to handle multiple document templates at once without the complexity and clutter of traditional methods. Using Custom Pages, you can generate and organize documents across different entities directly within the Dynamics 365 environment, making it easy to scale your solution for any table or scenario. Let’s take a closer look at how Custom Pages can streamline and simplify document management for your organization. The Use-Case: Document Management Application Key Components of the Solution which I have chosen for this use-case and blog Step-by-Step Process Step 1: Create the Custom Page (refer to my previous blog if needed) Create a solution, create custom Page and then embed it into Model-Driven App. I’ve made a sample example below: Step 2: How to retrieve parameters when App is opened. For the App’s ‘OnStart’ property, enter the following code Step 3: Trigger Document Generation App (I have used a ribbon button to trigger using JS) You will need to write a JavaScript in order to trigger and display the Custom Page. Where to find the app name, you will find in the solution. My example is below Step 3: Trigger Document Generation Page Once the document is created, you can close the Page using X button. As per JS code, our code will navigate to Document Tab. Ensure the name of Document Tab is correct. Step 4: Automation to SharePoint Use PowerApps Connector and add your input parameters to it. In the Custom Page, do insert the newly created Power Automate flow and pass the input values respectively Also, once the flow is completed, you can send a response back to Custom Page using same connector but of different action ‘Respond to PowerApp or Flow’. Conclusion Conclusion This Custom Page use-case demonstrates how a thoughtfully designed solution can enhance productivity and user experience in Dynamics 365. By streamlining document creation and navigation, it reduces friction in day-to-day operations, empowering teams to focus on higher-value tasks. Whether you’re a technical developer or a functional consultant, this approach provides actionable insights for building powerful and efficient solutions. References We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfonts.com. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut elit tellus, luctus nec ullamcorper mattis, pulvinar dapibus leo.

Introduction In this guide, I’ll Walk you through creating your first PowerApps Custom Page in Dynamics 365. This beginner-friendly approach will demystify the process and include a high-level use-case to inspire your developing use-cases in creative and simple way. Why are Custom Pages good? Custom Pages are Model-Driven exclusive Pages that can be used with Dataverse/CRM easily, it can bring flexibility and power to your Model-Driven Apps by allowing tailored layouts, interactive designs, and seamless integration within Dynamics 365. Custom Pages supports Power FX commands which are not present in Canvas Apps. Step-by-Step Guide to Creating a Custom Page Step 1: Prerequisites and Environment Setup Ensure users have the necessary permissions and access to PowerApps Studio and Dynamics 365.Also, prefer using Solutions as pages are seen in solutions but not in Apps section. Step 2: Create a New Custom Page There are 2 ways to create Custom Page, I will highly recommend 1st point but 2nd point is also there for your knowledge. You will land to PowerApps Editor screen for Page after this Add desired content to the Page as per your use-case, for the blog purpose, I made a contacts page. Save your Custom Page and Publish it. [Note: Do save and publish the App] Step 3: Embed the Custom Page in Dynamics 365 Model-Driven App To add the newly created Page in your Model-Driven App, add the Model-Driven app to your solution and click on Edit For showing it on the Navigation Menu, do select checkbox. But if you want to show it Page as on-demand style/pop-up or JS triggered style then simply add the page to Model-Driven and hide it on Sitemap. [Note: Once completed, Do save and publish the App] Final Output Your Custom Page will be embedded directly to the Model-Driven App. That’s all for creating Custom Page in Model-Driven App. Conclusion Creating a Custom Page in D365 is a simple yet powerful way to enhance your Model-Driven Apps. With this guide, you’re ready to start building interactive, dynamic solutions tailored to your business needs. Hope my blog helps you! We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfonts.com. Reference Links Microsoft documentation: Understanding Custom Page Microsoft Documentation: Create Custom Page Microsoft Documentation: Calling/Navigating to Custom Page

What Makes Custom Pages Unique? Key Differences Between Custom Pages and Canvas Apps Benefits of Using Custom Pages in D365 Conclusion In conclusion, Custom Pages stand out as a powerful tool for enhancing the functionality and user experience within the D365 ecosystem. By offering seamless integration with Model-Driven Apps, advanced design capabilities, and tailored interactions, Custom Pages provide users with a dynamic, responsive interface that feels native to the D365 environment. While Canvas Apps offer broader cross-platform flexibility, Custom Pages excel in scenarios requiring deep integration and advanced Model-Driven functionalities. Whether you’re looking to improve user engagement or create personalized, context-sensitive workflows, Custom Pages offer a unique advantage, making them an essential tool for any D365 implementation. We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfonts.com. Reference Links PowerApps Custom Page: Microsoft Documentation – Custom Page

Introduction Microsoft Power Apps is a pivotal tool for creating custom apps tailored to specific business needs. A powerful feature of Power Apps is the ability to display associated records on the main grid form using Grid Control. This functionality provides users with a comprehensive view of related data, enhancing user experience and productivity. In this blog, we’ll explore how to effectively display associated records on the main grid form using Power Apps Grid Control. Steps to Display Associated Records Open your Power Apps Studio. From the Power Apps homepage, go to the Tables section. Select your desired table. In this case, it is the ‘Task’ entity. Go to the View Section on the ‘Task’ Entity. Select the desired view such as ‘All Tasks’ Click on ‘Components’ from the Navigation Bar Click on ‘+ Add a component’ followed by ‘Get more components’. This will open a library of available components that you can add to your table. Choose ‘Power Apps grid control’ and click ‘Add’ below. This control allows you to customize how data is displayed within the grid, including the ability to show related records. It will be present in the control list like this. Select it. In the Power Apps grid control settings, select the related entity for which you want to display the associated records. For example, if you want to display users assigned to tasks, choose ‘Assigned Users’. Click ‘Done’ After configuring the grid control, save your changes to the app. Make sure to test the configuration to verify that the associated records are displayed as expected. Once everything looks good, publish the app to make the changes live for all the users.Voila, you see the Assigned Users’ Associated Records on the View. Conclusion By effectively utilizing Microsoft Power Apps Grid Control, you can significantly enhance the user experience by providing a comprehensive view of associated records directly on the main grid form. This step-by-step guide equips you with the knowledge to configure and display related data, streamlining your app’s functionality and improving productivity. We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Hi All, Have you ever wondered how to use Dataverse In-App notification that can be helpful in many scenarios, I’ll give an overview of the usage with a use-case. Documentation Link Business Insights in Real-Time – Documentation This is the In-App Notification Let’s see how to create such an In-App notification Step 1: In order to use this In-App notification, we need to enable it. -> Go to Editor of Model-Drivel App -> Click on Settings -> Click on ‘Features’ -> Enable ‘In-App Notification’ Note: This In-App notification creates records in Dataverse, therefore the storage will be consumed. There’s also a time-based auto-deletion that can be configured by Admin. Step 2: Save & Publish your Model-Driven App. You will see a Bell Icon on the top-right of the App. Step 3: Now, we will create the notification. There are 3 ways to create the notification, Using JavaScript -> will be using in this example Using C# Plugins (Dataverse SDK) Using HTTP Request (Web API) Step 4: As example, I will be sending a Notification to me but you can configure it to send to anyone in the organization. Note: You must have the necessary permissions to do so, Admin can configure these privileges by customizing Security Roles for the ‘app notification‘ table Refer what type of format you want to display from the documentation link provided above Step 5: I’ve created a Web-Resource that triggers when I manually close the case, So when I close a case, here’s the output. Note: You can automate these and send to anyone.Some examples are:1. Automatic send Notification of new case created to assigned person.2. Automatic notification to the Team whenever a critical ticket is raised.3. Apart from these, you can have notification whenever a Business critical flow has been failed. Some of the best ways to use is with having rich user experience with Icons and formatting options that are available to use.Icons, font styling and mentioning anyone That’s how we can achieve In-App notifications. Hope this helped you!

The Organization Data Service is an OData v2.0 endpoint introduced with Dynamics CRM 2011. The Organization Data Service was deprecated with Dynamics 365 Customer Engagement v8.0 in favor of the Web API, an OData v4.0 service. For more details please follow the link https://powerapps.microsoft.com/en-gb/blog/odata-v2-0-service-removal-date-announcement/ OData v2.0 Service removal date announcement | Microsoft Power Apps To determine the deprecation in your old javascripts below is the blog you can refer to. Step 1: Log in to the required Power Apps environment using the URL make.powerapps.com by providing a username and password and select your environment accordingly. Step 2: Go onto Solutions and click on [+ New solution] from the menu bar Step 3: Name your Solution and fill in all the details which include the Publisher as well as the Version details. Step 4: Go inside your solution and select Add existing option. Click on More and select Web resource. Step 5: Search for your web resources using your custom publisher. For example, your publisher might be new_ or abc_ and so on.It depends on how you name your publisher. Step 6: Select all the web resources you required and once done, go back to the solution and click on the ellipses(3 dots) of your solution. Click on the option Solution checker and select Run. Step 7: We can also view the Run Status of the solution. Step 8: Click on Ellipses(3 dots) again of the solution you have worked on and click on Solution checker and then you can view the option Download results. Click on that option and once you download it, it will be downloaded in the form of xlsv(excel). Try searching the issue for web-avoid-crm2011-service-data on that excel sheet. Hope this helps!!!

Introduction Let’s say you come across a scenario where you want to show dynamic records for your gallery items based on previous record details. For example: Let’s say a basic Q&A where the User should input data and then proceed.So, I have created something similar that will help in developing such a design quickly and efficiently. Steps to implement in Canvas PowerApps Step 1: Create a collection that will store data of the gallery. (You can use Dataverse records here with the unique identifier in the collection.) Note: Collection is better to use if you are referring to the same table. If you use Gallery.AllItems then you will encounter errors and circular reference issues. Set a Blank Vertical Gallery where Items property is as follows: Step 2: Add a Text Input in Gallery that will accept the User’s Input Along with Questions. Conclusion That’s all. You got dynamic content based on previous values. I hope this helps!

The Sign In Page of a Power Apps Portal looks something like the image as shown below.  The components shown in different colors in the below image are on the portals login page, we cannot access the backend code of these components but we can rename disable enable these components so let’s see how to do this.  When you provision your power apps portal with the portal a “Portal Management” Model-driven app is also being deployed in your environments.  In this Portal Management app, there are site settings using which you can enable/disable the Sign in Page Components    Below is the list of site settings whose values (true/false) enable or disable components on the sign-in page.   Authentication/Registration/AzureADLoginEnabled – Enables / Disables Azure AD Button.  Authentication/Registration/ExternalLoginEnabled – Enables / Disables Externa SignIn Section  Authentication/Registration/Enabled – Enables / Disables the registration section.   Authentication/Registration/InvitationEnabled – Enables / Disables the invitaion redeem button   Authentication/Registration/LocalLoginEnabled – Enables / Disables the local login section   Authentication/Registration/OpenRegistrationEnabled – Enables / Disables Registration button.  Search/Enabled – Enables / Disabled search icon on the screen.  Hope this helps!  Thank you.