Describe application lifecycle management Application lifecycle management (ALM) is a cyclical paradigm for the development, governance, and maintenance of applications, as illustrated in Figure 2-10. Power Platform supports an ALM strategy that uses Power Apps, Power Automate, and Common Data Service components packaged as a solution. FIGURE 2-10 The lifecycle of an application By packaging the components of an ALM strategy as a solution, administrators can import them into the Common Data Service in other environments. This allows developers in those other environments to access the ALM components when developing their own apps and flows. Describe business process flows Business process flows are tools thatRead More →

Power BI Desktop data types Power BI Desktop includes a larger set of data source connections from which developers can choose and a tabbed interface that provides simpler access to them: ■ All—Contains a list of all the connections found on the other tabs ■ File—Contains connectors for Excel workbooks, text files, SharePoint folders, PDFs, and other standard file formats, as shown in Figure 3-53 FIGURE 3-53 The File tab in Power BI Desktop’s Get Data dialog box ■ Database—Contains connectors for many of the standard commercial database formats, including SQL, Access, Oracle, IBM Informix, Sybase, and SAP, as shown in Figure 3-54 FIGURE 3-54Read More →

Describe use cases for shared data sets and template apps and how to consume each Shared data sets and template apps are ways for Power BI users to function as content developers without a great deal of experience manipulating data or Power BI constructions. Using shared data sets Obtaining and modeling data are the first—and arguably the most important—parts of creating a report or dashboard in Power BI. These steps can be complicated and require a lot of time and effort, so Power BI makes it possible to share data sets with other users. This way, developers do not always need to have a completeRead More →

Skill 3.3: Build a basic dashboard using Power BI A dashboard is a single-page Power BI document, like the one shown in Figure 3-61, that presents consumers with a selection of tiles containing highlights from one or more reports. The object of a dashboard is to tell a story relatively concisely, in relation to a report. It is assumed that if the consumers require more information, they can simply look at the report(s) from which the dashboard tiles came. FIGURE 3-61 Sample Power BI dashboard This skill covers how to: ■ Design a Power BI dashboard ■ Design data layout and mapping ■ Publish andRead More →

Design data layout and mapping The combination of the pinned visualizations from reports and the additional material available through the Add tile dialog box allow developers to design dashboards that tell a specific story to the consumers and provide them with access to more detailed information in the reports themselves. Deciding what information needs to appear on a dashboard and how that information should be visualized is an important part of the dashboard design and creation process. Designing for screen size Because a dashboard is only a single page, developers must consider the size of the screen that consumers will be using to view it.Read More →

Publish and share reports and dashboards After creating a report or dashboard in the Power BI service, developers can share it with selected users. These users then become consumers of the content, meaning that they can view the material and interact with it (by adding comments, for example), but they cannot edit it.  Exam Tip To share content, both the developer and the consumer must have Power BI Pro licenses or be working in a Power BI Premium workspace. Candidates for the PL-900 exam can access the free version of Power BI, but to work with the sharing features, they can obtain a trial versionRead More →

Describe use cases and limitations of business rules Business rules enable developers to implement logic on data stored in Common Data Service. Because the rules apply to the data, and not to a specific app, they take effect however the data is used. For example, if the value of the Country field in an entity is entered as Canada, a business rule can enable a six-digit alphanumeric Postal Code field and hide the five-digit numeric Zip Code field used for U.S. addresses. Business rules consist of conditions and actions. Conditions are circumstances that must be met for the rule to apply, and actions are theRead More →

Describe the Common Data Model (CDM) As discussed earlier in this chapter, Common Data Service can function as a database for the Power Platform tools, as well as for Dynamics 365. While Common Data Model sounds similar to Common Data Service, it is not the same thing. CDM is not a database manager or any sort of data storage technology. Instead, the Common Data Model (CDM) is a Microsoft initiative that defines a shared data language, consisting of a unified system of schemas and metadata. The objective behind CDM is to create a standardized format for data sharing and storage that allows applications and servicesRead More →

Skill 2.2: Describe connectors Connectors are the Power Platform components that allow Power Apps and Power Automate to interact with outside applications, services, and data files and utilize their data. Well over 200 public connectors are available to Power Platform users, and for those applications and services that are not supported, it is possible for developers to create custom connectors. A connector is a proxy wrapper that Power Platform tools use to access an application programming interface (API) provided by an application or service. Many applications and cloud services have the necessary APIs, and the Power Platform connectors function as proxies, or intermediaries between theRead More →

Identify use cases for custom connectors As mentioned earlier, a connector is a wrapper that surrounds a REST API supplied by the application or service that will be the data source. Power Platform provides connectors for a great many applications or services, but certainly not for every one. For developers that require access to data sources for which there are no public connectors available, it is possible for them to create their own custom connectors. When a developer creates a custom connector, it is part of the current working environment and is usable only by the apps and flows operating in that same environment. ItRead More →