Microsoft Power Platform - Getting Started

Overview

I have been preparing for the PL400 example and thought to share my learnings with this. In this article I will be giving you a brief overview of the components of Power Platform which are based on the learning materials available on the Microsoft certifications site.

Power Platform uses environments to store, manage and share data for an organization.

For every new environment a dataverse instance is created which will host the Database. 

This will be then be utilized across other technologies, such as Apps and Flows


For administrative requires use the Power Platform admin center

Includes the following;


Other portals

- Power Automate - for automated flow

- Power BI - for reports

- Power Virtual Agents - for chatbots

- Power Pages - for websites

Security

- Has policies an procedures for data loss prevention to prevent organizations from unintentionally exposing data

Connectors are as follows
- Non - Business - for data related to personal use. Default (data from here can be moved to Business and Blocked)
- Business - for data related to business

- All data is managed within TLS connection
- Accessibility checker can be used for verifying access

- Blocked - for data related to restricted access.

Microsoft Dataverse

- Available globally
- Deployment is restricted to its geographical location
- Incorporates security, logic, data and storage in a central point
- All data is stored in dataverse
- Any business solution can connect to supports large datasets and complex data models

Tables 

Stores data within columns and rows defined. 

Table types:
- Standard - available as part of the solution, can be modified
- Managed - cannot be modified
- Custom

Relationships

- Uses business rules to define additional logic on fields or columns
- Helps to normalize data

Dataflows
- Are self-service, cloud based data preparation technoly

Connectors
- Allows business solutions to connect data across platforms

Available connectors
- Data sources - two type, tabular and function based
- Triggers and actions
- Standard connectors
- Premium connectors
- Custom connectors

An example dataverse table creation





Comments

Post a Comment

Popular posts from this blog

D365FO - Create a multi-select lookup in batch jobs

Image
D365FO - Create a multi-select lookup in batch jobs In this article, I will be describing how we can create a multi-select lookup for display within the batch job dialog. Contract class Create a new variable of type 'List'. This will store the selected values of the user for the dropdown from the dialog. Create a parm method to access the new list object Ensure to specify the DataMember attribute Add an appropriate label Specify the data type for the list's content Ensure to specify the DataContract and SysOperationContactProcessing attributes above the class declaration. An UI builder is also required. The requirements for this is explained in the next section. Example: UI builder class Create an UI builder class that extends SrsReportDataContractUIBuilder Add a new variable of type 'DialogField'. This will be displayed on the UI for user. Implement the postBuild method. Initialize the contract from this.dataContractObject() and bind the dialog field variable to th...
Read more

Generate and download a csv file using X++

Within Dynamics 365 HQ we often need to be able to export data as a csv file. This article explains how we can generate a csv file. The following lines of code can be used to create and download a csv file Create a writable stream. CommaStreamIo streamIO = CommaStreamIo::constructForWrite();   streamIO.writeExp('Id', 'Title'); // These will represent the header of the csv file  streamIO.writeExp('001', 'Science'); // Row 1 streamIO.writeExp('002', 'Nature'); // Row 2 // Get the stream System.IO.Stream        stream              = streamIO.getStream(); const str               extensionCsv        = '.csv'; stream.Position = 0; // StreamReader to read as str System.IO.StreamReader...
Read more

Creating a batch job with query based filter in D365 back-office

There are often business processes that requires us to run specific operations as a batch process. Dynamics 365 Head quarters (HQ) allows us to be able to periodically execute batch jobs. To create a custom batch job you need to extend the  RunBaseBatch class. The following lines of code show how we can create a simple export job.  class InvoiceExport extends RunBaseBatch {      Query                   query;     QueryRun                invoiceQueryRun; // QueryRun object that will be used to generate data for invoices to be exported.      DialogGroup             dialogGroupSetup; // This is a dialog group.     DialogField      ...
Read more