© The Author(s), under exclusive license to APress Media, LLC, part of Springer Nature 2022
S. Prakash PradhanPower Platform and Dynamics 365 CE for Absolute Beginnershttps://doi.org/10.1007/978-1-4842-8600-5_8

8. Working with Power App Configurations

Sanjaya Prakash Pradhan1  
(1)
Ganjam, Odisha, India
 

Power Apps provides many configurable components that you can configure based on your business needs. Its model-driven apps have personalization and advanced settings.

Using the personalization settings, you can set your personal preferences, which are applicable to you only. Using the advanced settings, you can configure settings that are applicable to all users.

Admin Centers and Their Uses

Table 8-1 lists the important links to various admin centers in Power Apps.
Table 8-1

Admin Center Links

Microsoft 365 Admin Center: Use this Admin Center to add/modify users and products and to add licenses to users.

https://admin.microsoft.com/

Power Platform Admin Center: Use this to manage environments and add users to the environment and other settings.

https://admin.powerplatform.microsoft.com/environments

Power Apps Admin Center: Points to the same Power Platform Admin Center.

https://admin.powerapps.com/

Dynamics 365 Advanced Settings: Use this to manage the advanced settings.

https://[orgname].[region].dynamics.com/main.aspx?settingsonly=true

Power Apps Maker Portal: Use this to create and manage Power Apps.

https://make.powerapps.com/

Azure Active Directory: Use this to manage the Azure app registration and the Azure settings.

https://aad.portal.azure.com

Power BI Admin Center: Use this to define the Power BI settings.

https://app.powerbi.com/admin-portal/tenantSettings

Preview App Maker: Use this to see the preview features.

https://make.preview.powerapps.com/

Office Home Page: Use this for all apps on the Office dashboard.

https://www.office.com/

Personalization Settings

To configure personal settings, click the gear icon on any model-driven app from the top bar and choose Personalization Settings. Figure 8-1 shows this process.

A window has the settings option selected with a context menu that has options in rows labeled personalization settings, advanced settings, about, privacy and cookies, and software license terms.

Figure 8-1

Settings in Power Apps

In the Personalization Settings, you will see many options, such as General, Synchronization, Activities, Formats, Email Templates, Email Signatures, Email, Privacy, Language, and so on.

Set the Default Pane Option

You can set a default pane so that when you log in, your default pane automatically loads.

In the Personalization Settings, General tab, change the Default pane and Default Tab. Click OK after you do the update. Figure 8-2 shows the General Personalization Settings options.

A segment of a window titled set personal options has two dropdown boxes on the same row, each is boxed. On the left, the default pane has students info selected, and on the right, the default tab has students selected.

Figure 8-2

General personalization settings

Now when you open the app, the Student Info area and Students tab will load as the home page by default.

Change Record Count Per Page in Views

When you load an entity view, it displays 50 records of that entity per page by default. You can increase the records count per page using the settings in Figure 8-3.

A segment of a window has text that reads Set the number of records shown per page in any list of records. On the left, it has a label, records per page, with a dropdown box on the right, where 100 is selected.

Figure 8-3

Changing the per page record count

The result will now show 100 records per page, as shown in Figure 8-4.

A window of Dynamics 365. From the top, it has a search and menu bar. Below, on the left, it has a navigation pane, where accounts is selected. Accounts page is at the right side, listed with 9 rows of account names. On the bottom part, a label that reads 1-100 of 101 is boxed.

Figure 8-4

Per page record count has been changed to 100

Time Zone and Default Currency Setup

You can configure the default currency of your customers and the time zone you are in. This way, records that use the time zone and currency will be set properly. Figure 8-5 shows the time zone and currency options.

A segment of a window has two text labels that read set the time zone you are in, with a dropdown box below, where G M T, plus sign, 05.30, Chennai, Kolkata, Mumbai, New Delhi is selected, and set a default currency, where Canadian Dollar is selected.

Figure 8-5

Time zone and currency options

Email Templates and Signatures

You may find that you often send very similar emails to customers, with some dynamic values being the exception. For example, when you send a welcome email to customers, the content might be the same except for the salutation and the customer’s name. For these types of scenarios, you don’t want to have to re-type the same content every time. Instead, you can configure email templates that contain reusable content in the email body with dynamic values. You simply need to click Send. This is a time-saving tool you can use in your day-to-day business dealings when sending emails.

To create a new email template, click the New option. Figure 8-6 shows the process of creating a new email template.

A segment of a window has the email template on the menu column selected. Below, a column labeled new is boxed.

Figure 8-6

Creating a new email template

You can select a global template or an entity-specific template. Figure 8-7 shows the process of creating a global template.

A dialog box titled Email Template type, with details below that reads select a template type to use for this new email template has a dropdown box below, where row 1, global, is selected.

Figure 8-7

Creating a global template

For the global type, you can use dynamic field values from the User entity only. For the entity-specific type, you can use user entities and targeted entity-specific field information in the template. This example sets the Type to Contact and shows how to configure the template.

Give the template a name and set the Permission level to Individual. If you set Permission level to Organization, anyone from your organization can use the template.

Choose English for the Language and provide a description. In the subject, specify a common subject of the email. In the body, add the content. To insert dynamic content, click the Insert Dynamic Text button and select the corresponding field so that when the template is used, the value will render dynamically. Figure 8-8 shows the process of inserting dynamic content inside a template.

A window with a column labeled insert dynamic text is boxed. Atop is a dialog box titled Edit dynamic test with a box that has two dropdown boxes, with contact and full name selected. Then followed by an empty text box for default text. Below, on the bottom right corner are two command buttons labeled insert, and cancel. Insert is boxed.

Figure 8-8

Inserting dynamic content inside a template

After the data is filled in, click the Save button. The final template will look like Figure 8-9.

A window titled Welcome Email Template for New Contact. It is in the template section with 2 boxes named details and the Template editor below. Under details, it has details, which are name, permission level, category, language, and description. Under template editor is a text box for the subject and the body of the email.

Figure 8-9

Individual scope template

After you successfully create an email template, it’s time to create an email signature. Click the Email Signature tab and choose the New option. Figure 8-10 shows the Email Signature configuration page.

A segment from a window has a column labeled email signatures selected and boxed. Below, an option labeled New is boxed.

Figure 8-10

Email signature configuration options

In the Signature screen, provide a signature and save it. You can mark a signature as the default so that the signature will be copied into the email body. Figure 8-11 shows the process of saving a template record with the Default option set to Yes.

A window of Dynamics 365 has a menu and search bar at the top, and a navigation pane on the left, where row label email signatures are selected. On the right, the option labeled save, row label set as default with yes, and salutation on the email body that reads regards, Sanjay Prakash, Microsoft M V P are boxed.

Figure 8-11

Saving a template record with the Default option set to Yes

You can use the email template to send an email to a contact. Open a contact and click Related Activities. Choose New Email. Figure 8-12 shows the process of adding an email activity for a customer.

A window of an email page has box labels, from top to bottom, which are contact dot contact, activities, new activity, and email on the fourth row in a context menu.

Figure 8-12

Adding email activity for a customer

Now choose Insert Template and choose the template you created. Figure 8-13 shows the process of choosing an email template while sending an email.

A window has a column labeled insert template boxed. Atop is a dialog box with a navigation pane on the left with a row labeled welcome email template for new contact selected and boxed. On the right, the email is boxed.

Figure 8-13

Choosing an email template while sending an email

Advanced Settings

Advanced settings are applicable organization-wide. To navigate to the advanced settings, go to make.powerapps.com and choose the correct environment. Click the gear icon to select Advanced Settings. Figure 8-14 shows the Advanced Find option.

A window has a menu bar at the top, followed by icons of Microsoft Excel and S Q L on the left, below, and a navigation pane of settings with advanced settings boxed on the right.

Figure 8-14

Advanced find option

This will open the Advanced Settings screen. In this screen, you will find many options that you can configure, including Business settings, Customization settings, System settings, Process Center settings, and so on. Figure 8-15 shows the Advanced Find screen with links.

A window of Dynamics 365 under the settings section. It has 7 column headers, which are business with 6 row labels, customization with 5 row labels, system has 2 columns with 6 and 5 row labels, process center with 2 row labels, portals, extensions, and application.

Figure 8-15

Advanced find screen with links

In this chapter, you will learn about some of the important settings for model-driven Power Apps.

Data Import in Power Apps

Using the Data Import feature, you can import data from Excel files into Dataverse entities. Say you store student records in an Excel sheet and want to import them to the Dataverse. You can use the import feature to do this. Use the following steps to do this.

Step 1: Prepare a Raw Excel Sheet

The first step is to prepare an Excel sheet with data. The Excel sheet in Figure 8-16 contains student records with their full name, mobile number, email, and gender. You’ll see how to import this data into a Dataverse table.

An Excel worksheet. Under A column in rows 1 to 3 are full name, Clyde Richards, and Robin Richards. Under B column are email, clyde at gmail dot com, and robin at gmail dot com. Under C column are mobile, 1111222211, and 8888666677. Under D column are gender, female, and male.

Figure 8-16

Importing Excel data into a Dataverse table

Save the file in the .CSV (comma-delimited) format. Figure 8-17 shows the Save As option.

A dialog box, with the file path in the address bar in order, which are this P C, downloads, codes, and c s v. On the left, it has a navigation pane. At the bottom part, it has a text box of file name labeled students dot c s v, and a dropdown box of file type, with C S V selected. On the bottom right corner are 2 command buttons save and cancel.

Figure 8-17

Saving a file as a .CSV file

Step 2: Upload a CSV File

Once the CSV file saved, navigate to the Advanced Settings screen in Power Apps and click the Data Management option. Figure 8-18 shows the Data Management option.

A window of Dynamics 365 under the settings section. It has 7 column headers, which are business with 6 row labels, customization with 5 row labels, system with 2 columns with 6 and 5 row labels. Data management, under column system is boxed.

Figure 8-18

The Data Management option

Click the Data Imports icon and, from the command bar, choose Import Data. Figure 8-19 shows the Import Data option.

A segment of a window has header imports, with detail below that reads import data and view the status of imports in progress. Below is a row with columns labeled export to Excel and import data.

Figure 8-19

The Import Data option

The Import Data option will open a window where you can browse the CSV file for processing.

Click the Browse link and select the CSV file. Then click Next. Figure 8-20 shows how to choose the .CSV file to import.

A dialog box titled upload a data file has a box below with a command button choose file and a text box with label students dot c s v, boxed. On the bottom right corner are the command buttons next and cancel.

Figure 8-20

Choosing the .CSV file to import

On the next screen, you can review the file upload and click Next. On the next screen, choose Default Mapping and click Next. Figure 8-21 shows the default mapping option.

A segment from a window has a text box labeled System Data Maps with details below that reads default, automatic mapping.

Figure 8-21

Default mapping option

Step 3: Map an Entity and its Fields

In the next step, you need to map a correct entity and field. Figure 8-22 shows the mapping table.

A window has a segment labeled Map Record Types. From the top, it has a box labeled the data files have been successfully mapped to the target Microsoft Dynamics 365 record types. Below are columns labeled source data files with row entry student, with a check sign, and Microsoft Dynamics 365 Record Types with row entry student.

Figure 8-22

Mapping table

After your entity has been mapped, click Next for Field Mapping. Figure 8-23 shows the mapping columns.

A window titled Map Fields, from the top has a box labeled all the record types with fields have been successfully mapped. Below, on the left, is a box with column header Dynamics 365 Record Types with row entry student. It has 2 columns on the right labeled source fields with row entries required fields and optional fields, and dynamics.

Figure 8-23

Mapping columns

Once the fields have been correctly mapped with the Dynamics 365 entity, click Next to review. Then click Submit to finish the steps.

Now a new background import process instance that will run in the background to import data. Figure 8-24 shows the import result.

A window of Dynamics 365, under data management, has a table titled my imports. It has column labels import name, student reason, success, partial failure, errors, total, created on, and created by. On the second column, row entries student dot c s v and submitted are boxed.

Figure 8-24

Import result

After some time, if you refresh the data import operation, you can check its status. Figure 8-25 shows the import success.

A table has eight columns and a row. The column headers are import name, status reason, successes, partial failures, errors, total, created on, and created by. Each row entries, which are students dot c s v, completed, 2, 2, and 4.26.20221 1 are boxed.

Figure 8-25

Import success

Now you can navigate to the Students view and see if all the records have been imported successfully. Figure 8-26 shows the import success records.

A table titled Active Students has 5 columns and 3 rows. Name has row entries Clyde Richards, Richi Sharma, and Robin Richards. Created on has row entries 4.26.2022 1.18 PM, 4.26.2022 10.07 AM, and 4.26.2022 1.18 PM. Email has row entries clyde at gmail dot com and robin at gmail dot com. Mobile number has row entries 1111222211 and 8888666677.

Figure 8-26

Import success records

This shows that you have successfully imported the student records into the Dataverse.

Configure Duplicate Detection Rules

Duplicate detection rules can be configured to determine if a record is a duplicate of another record by configuring matching fields. Duplicate detection checks are enforced while creating new records and updating existing ones. You can also enable duplicate detection rules when importing data.

To enable duplicate detection rules, navigate to the advanced settings and, from the Data Management option, select Duplicate Detection Settings.

You need to enable the duplicate detection rule settings and then configure the rules. Figure 8-27 shows the Duplicate Detection option.

A window Dynamics 365 has a row labeled duplicate detection settings, with detail below that reads select default duplicate detection settings for your organization.

Figure 8-27

The Duplicate Detection option

In the Settings screen, enable the Enable Duplicate Detection checkbox and, in the Detect Duplicate options, enable the following options:
  • When a record is created or updated: This option will check for duplicate records when creating new records or updating existing ones.

  • When MS Dynamics 365 for Outlook goes from offline to online: This option will check for duplicates when you are offline and you created some records and duplicate record has not been checked. Once you are back online, the duplicate checks will run.

  • During data import: This option will check for duplicates during the Data Import operation.

Figure 8-28 shows the Duplicate Detection settings.

A window titled duplicate detection settings has four checkboxes under the row label, enable duplicate detection. On the bottom right part are command buttons O K and cancel.

Figure 8-28

Duplicate Detection settings

Click OK after enabling these settings. Now you need to configure the rules. Click the Duplicate Detection Rules option, which is shown in Figure 8-29.

A window has a segment named Duplicate Detection Rules, with detail below that reads create, modify, and publish duplicate detection rules.

Figure 8-29

Duplicate Detection Rules option

This will open all the duplicate detection rules configured in the system. You can create your own rules. Click the New option to do so. Figure 8-30 shows the list of available Duplicate Detection Rules.

A window named Duplicate Detection Rules has a table that has four columns and nine rows. Column entries from columns 1 to 3, and row entries from rows 1 to 8 are boxed.

Figure 8-30

List of available Duplicate Detection Rules

In the New Rule screen, specify the name for the rule. Say you want to create a duplicate rule for the Students entity. If two students have the same email ID, those are duplicate records.

In the New Rule screen, set Base Record Type to Student and Matching Record Type to Student.

In the Rule Criteria, select the Email field. For Criteria, choose Exact Match. Save the rule and publish it.

If you don’t publish the rule, it will not work. Every time you create a duplicate detection rule, you need to publish it. Figure 8-31 shows the configuration screen for the Student Duplicate Email rule.

A window titled Duplicare Detection Rule, Students with Same Email Rule, under information. On the left, it has a navigation pane, and on the right, it has text boxes under details name, description, base record type, and matching record type. Below is a table with headers field, criteria, number of characters, and ignore blank values.

Figure 8-31

Configuration screen for the Student Duplicate Email rule

Once the rule is published, you can test it. Create a new student with an email ID and save it. Now create another student with the same email ID. You will see the Duplicate Records screen shown in Figure 8-32.

A dialog box named Duplicate record found has a text box of duplicates found labeled with Student, 1. Below is a table that has three columns and a row. The column headers are name, modified on, and email. On the bottom right corner are command buttons ignore and save, and cancel.

Figure 8-32

Duplicate record detected

You can either ignore the warning and save this field with duplicate data or you can cancel the save operation.

You can merge new record information with duplicate records and configure multiple duplicate detection rules for a single entity.

Configure the Auditing Feature in Power Apps

The Auditing feature logs changes that are made to customer records and user access so you can review this activity later. The Auditing feature is designed to meet the auditing, compliance, security, and governance policies of many regulated enterprises.

To enable the Auditing feature, navigate to advanced settings and select the Auditing option. Figure 8-33 shows the Auditing feature.

A window of Dynamics 365 under the settings section. It has 3 column headers, which are business with 6 row labels, customization with 5 row labels, system with 2 columns with 6 and 5 row labels. Auditing, under column system is boxed.

Figure 8-33

The Auditing feature

Follow below sections to enable auditing in Power Apps.

Enable the Global Audit Settings

From the Auditing option screen, click Global Audit Settings. Figure 8-34 shows the Global Audit Settings option.

A window has a segment named Global Audit Settings, with a detail below that reads select audit settings for your organization.

Figure 8-34

Auditing global settings

Enable the Start Auditing option and other required options based on your business needs. You can enable User Access Audit, Read Access Audit, and common entities including custom entity audits. Figure 8-35 shows how to enable the Global Audit.

A dialog box titled System Settings, under auditing has checklists under row labels audit settings and enable auditing in the following areas boxed. It has two command buttons on the bottom right corner, which are O K and cancel.

Figure 8-35

Enabling Global Audit

Enable an Audit at the Entity Level

The next step is to navigate to the corresponding entity and enable the Audit option. Say you want to enable auditing for contact entity mobile number. You have to click the Entity and Field Audit Settings, shown in Figure 8-36.

A window has a segment named Entry and Field Audit Settings, with a detail below that reads enable audit tracking on selected entities and fields.

Figure 8-36

Entity and Field Audit settings

When the screen open, expand the entity node and select the contact entity. In the Contact Entity Settings screen, enable the Audit flag.

After that, navigate to the Fields node and select the field you want to audit. In the Fields settings, enable the Auditing flag. Figure 8-37 shows this process.

A window with a boxed row labeled contact on the navigation pane points to a boxed check box labeled auditing on the bottom part.

Figure 8-37

Selecting an entity for auditing

Enable field-level auditing. Figure 8-38 shows the select columns for auditing.

A window with row labels in navigation pane, which are contact and fields, and row entry with name of mobile phone are boxed. Row entry mobile phone points to row label auditing with bulleted label enable on a window box atop.

Figure 8-38

Selecting columns for auditing

Now you are done. You have successfully enabled auditing. You can test the feature now. Open a contact record and try to update a mobile phone number. Figure 8-39 shows the customer mobile number update screen.

A window of the summary under the account of Bijoy Kumar has a table with a column and five rows. The row headers are job title, account name, email, business phone, and mobile phone. Row entries mobile phone and 8777777 are boxed.

Figure 8-39

Customer mobile number update screen

Click the Related tab and choose Audit History. You will now see the old mobile phone and the new value with the Changed By value. Figure 8-40 shows this process.

A window of audit history under the account of Bijoy Kumar has a table with six columns and three rows. Row entries, which are Sanjay Prakash, update, mobile phone, and 8777777 are boxed.

Figure 8-40

Verify the audit data using the Audit History option

Add Users to Environments

You can add new users to an environment using Office 365 Admin Center. After you add new users, you can assign a license to them so that they can access correct apps and tables with security roles.

Use the following steps to add new users to your environment.

Step 1: Open the Admin Center and Add a User

Navigate to office.com and log in. Click the All Apps icon and choose the Admin icon. Figure 8-41 shows the Admin option of the Office home page.

A window of a list of apps in two columns in five rows, which are One Drive, Excel, One Note, Power Automate, Power Apps, Word, PowerPoint, Share Point, Admin, and Lists. Admin app is boxed.

Figure 8-41

Admin option of the Office home page

From the User option, choose Active Users and click Add a User. Figure 8-42 shows how to add a new user to the Dataverse.

A window of the Microsoft 365 admin center has a navigation pane on the left where the third row labeled active user is boxed. Under active user, on the menu bar, option add a user is boxed.

Figure 8-42

Adding a new user to the Dataverse

In the Add User panel, provide a first name, last name, display name, and username and then click Next. Figure 8-43 shows basic info about the user.

A dialog box titled set up the basics is on the basics phase. On the right, there are six textboxes with details to fill out, which are first name, last name, display name, username, domains, and password. On the bottom part is command button next.

Figure 8-43

Basic info about the user

In the next screen, select a license for the user and click Next. Figure 8-44 shows the process of assigning a product license to a user.

A dialog box titled assign product licenses is on the product licenses phase. On the right, there is a dropdown box, where option United States is selected. Below, under assign user a product license are 6 checkboxes in rows, where dynamics 365 sales premium and office 365 F 3 are ticked. On the bottom part are command buttons back and next.

Figure 8-44

Assigning a product license to a user

In the next screen, you can add more information about the user profile or you can skip that for now and click Next. In the last screen, you can review and finish. Figure 8-45 shows this process.

A dialog box titled review and finish is in the final phase. Below, it has row headers, which are assigned settings, display and username, password, product licenses, roles, and profile info. It has two command buttons labeled back and finish adding at the bottom part.

Figure 8-45

Finish adding a user

Now you have successfully added a user to your Office 365 system. You can now assign a security role to that user. You will learn more about security roles later in this chapter.

Go to https://admin.powerplatform.microsoft.com/ and select the correct environment. Click the Settings option. Figure 8-46 shows the process of selecting the environment settings.

A window of the Power Platform admin center has a navigation pane on the left where the second row labeled environment is boxed. On the right, on the menu bar, option settings are boxed. On the table, the first row of the environment column, development, is boxed.

Figure 8-46

Selecting environment settings

Click the Users option and then click User. Figure 8-47 shows this process.

A dialog box with the file path of environments, development, and setting has a search bar followed by row labels product, business, user permissions, and audit and logs. Under users plus permissions, row entry named users is boxed.

Figure 8-47

Choosing the Users option

Figure 8-48 shows how to add a user to the environment option.

A segment of a window has a menu bar where add user option is selected. Below are folder or file labels in order, which are environments, development, settings, and users.

Figure 8-48

Adding a user to the environment

Search for the user and click the Add option. Figure 8-49 shows the search process.

A window titled Add user has information and a header that reads user access requirements. Below is a text box with the label Rajeeb Kumar.

Figure 8-49

Searching for a user

This will add the user to the current environment. In the next step, you can select a security role that you want to assign to the user.

Figure 8-50 shows the process of adding a security role to the user.

A dialog box titled Manage security roles, from the top has a dropdown menu with soft chief dev option selected, followed by a column header role with row entries account manager, activity feeds, A I B Roles, A I B S M L Roles, and Analytics Report Author. Account Manager is selected. On the bottom right corner are command buttons save and cancel.

Figure 8-50

Adding a security role to the user

Select a security role and click Save. You have successfully created a user and assigned a product license with a security role. The user can log in to Dynamics 365 using their credentials.

If you want to enable some model-driven apps for the security role, you can go to the app and click Manage Roles. Watch this video to learn about giving security access to model-driven apps for users: https://www.youtube.com/watch?v=StsyOdUo6s4.

Security Matrix and Configurations

The security matrix is an important concept in Power Apps. You can configure different security matrixes for the following purposes:
  • Securing records from unauthorized users

  • Securing fields from unauthorized users

The security matrix combines access levels and privileges for entities to define a security role. On the top ladder of this security concept is the business unit.

Business Unit (BU)

A business unit is a logical grouping of related business activities. It is the foundation of the security structure in Microsoft Dynamics 365. Each user has to be part of a business unit. A default business unit is created when Dynamics 365 is installed.

Business units are hierarchical. One BU can be a child of another BU. In Figure 8-51, TATA is the root business unit. TCS and Tata Motor are immediate children BUs of TATA. Under TCS, there are two immediate children BUs—TCS India and TCS UK. Under TCS India, there are two children BUs—TCS East India and TCS South India.

A structural diagram of the T A T A. From the top, it has a column labeled T A T A. It is connected to boxed columns T C S and Tata Motor. The first boxed column, T C S, has two boxed columns below labeled T C S India that has T C S East India and T C S South India, and T C S The United Kingdom.

Figure 8-51

BU structure of the TATA example

So TCS India, TCS UK, TCS East India, and TCS South India, are child of TCS business unit. One user can be tagged with one Business Unit only. Multiple users can be tagged with the same business unit. One user cannot be tagged with multiple BUs. You can add multiple security roles to a business unit. All security roles of the parent BU are inherited by the children BU. Figure 8-51 shows the BU structure of this TATA example.

If you take the example of the School Management system, you can configure multiple business units per the organizational structure. You might want to manage your schools by geography, for example. In that case, the business unit structure could look like Figure 8-52.

A structural diagram of the Global School, from the top, has a column labeled Global School. It is connected to boxed columns G S India and G S The United Kingdom. The first boxed column, G S India, has two boxed columns below labeled G S South India and G S North India.

Figure 8-52

BU structure of the Global School example

As per a new enhancement, you can add multiple security roles to a user from one BU or multiple BUs.

Privileges

Privileges are actions that users perform on a record. For example, they can create, read, update, and delete records.

Access Levels/Depths

An access level defines the level or depth of access to a record item. There are five types of access level:
  • None: No record access.

  • User: Only access to records owned by the user who’s logged in.

  • Business Unit: Access to records owned by the user plus access to records created by other users belonging to the same business unit as the initial user.

  • Parent Child BU: Access to records owned by the user plus access to records created by other users belonging to the same business unit as the initial user belongs, plus access to records created by users from the child business unit of the initial BU.

  • Organization: Access to records belonging to the organization regardless of the business unit.

Security Role

A security role defines how different users, such as salespeople, access different types of records. To control access to data, you can modify existing security roles, create new security roles, or change which security roles are assigned to each user. Each user can have multiple security roles. You can create a new security role or modify existing ones.

It is always a best practice to open an existing security role and copy it to create a new security role instead of creating a brand new role from scratch.

To check security roles for a specific BU, click the Settings option from Power Platform Admin Center. Figure 8-53 shows the Security Roles option.

A window titled Power Platform admin center. On the left, it has a navigation pane, where the row labeled Environments is selected. On the right is the settings page with a dropdown box. Below are rows with headers labeled product, business, and users plus permissions. Below, a row labeled security roles is boxed.

Figure 8-53

The Security Roles option

Here you will see a list of security roles specific to a business unit. Figure 8-54 shows the security roles of the parent business unit.

A window of security roles under environments. From the top, it has a dropdown box with option soft chief dev selected. Below are columns with headers role and more actions. Roles has row labels account manager, activity feeds, A I B Roles, and A I B, S M L Roles. Each row labels has corresponding three-dotted symbol under more actions column.

Figure 8-54

Security roles of a parent business unit

Select a security role and click Edit. Figure 8-55 shows the Edit Existing Role option.

A window has a segment with column headers role and more actions. On role column, it has row labels, which are account manager, activity feeds, and A I B roles. Account Manager is selected, with its context menu on the right with row labels copy, edit, and delete.

Figure 8-55

The Edit Existing Role option

This will open the security role in Edit mode. Here you’ll notice many tabs, like Core Records, Marketing, Custom Entities, and so on. The tabs are defined based on the nature of the entities, such as Core Records. These are simply out-of-the-box entities and are gathered inside the Core tab. If you want to configure security access to an existing core or an out-of-the-box entity, you can click the Core Records tab and do the configuration. Click the Core Records tab. You will observe the privileges on the top row, the entities on the left panel, and the access levels at the bottom. In the middle portion, you define the matrix. To provide access to custom entities, you need to click the Custom Entities tab and search the entity from the list. Then you update the access level and privilege. Figure 8-56 shows the Access Levels and Privileges with Entity matrix.

A window titled Power Apps, under Security Role, Account Manager. On the left, it has a box with 19 rows, labeled as entities, boxed. On the right, columns labeled create, read, write, delete, append, append to, assign, and share labeled as privileges are boxed, followed by circles on the thirteenth row labeled matrix, which is also boxed.

Figure 8-56

The Access Levels and Privileges with Entity matrix

Let’s look at the matrix for the Account Manager Role. The matrix is denoted by circles in Figure 8-57. An empty circle means no access; a quarter-full circle indicates user-level access; a half-full circle indicates business unit-level access; a three quarters-full circle indicates a parent/child business unit-level access; and a filled circle indicates organization-level access.

A window has a segment that has 9 columns and 2 rows. The column headers are table, create, read, write, delete, append, append to, assign, and share. The row labels are shaded circles. On columns of create, delete, and assign, the circles are half-shaded. In columns read, write, append, append to, and share the circles are fully shaded.

Figure 8-57

Access level

This matrix shows that the Account Manager role has organization read access to the Account entity, which means account managers can read all account records available in the organization, regardless of business unit and owners.

The Account Manager role also has business unit-level delete permission to account records, which means account managers can delete account records that they created or that were created by other users in the same business unit.

The create, read, delete, write, append, append to, assign, and share privileges honor this security matrix. To copy an existing security role to a new security role, you can use the Copy Role option.

Field Security

To restrict access to the high business impact columns, you can configure field security profiles. This way, users of the profile cannot view those field values.

To configure a field security, go to the advanced settings and click the Field Security Profiles. Figure 8-58 shows the Field Security Profiles.

A window of Dynamics 365, under security, has row labels users, security roles, field security profiles, and positions. Field Security profiles with detail below that reads manage user and team permissions to read, create, or write information in secured fields are boxed.

Figure 8-58

Field Security Profiles

In the next screen, click the New option to create a new field security profile and give it a name. Say you want to hide the actual revenue field from a user named Rajeeb.

For this, you need to add the user using the Add User option. Figure 8-59 shows the process of adding a user to the field security profile.

A window of Power Apps has boxed labels, which are field security profile, opportunity revenue profile, users, located at the upper part, then users, located in the navigation pane on the left, and row entries Rajeeb Kumar and soft chief dev, located at the center.

Figure 8-59

Adding a user to the field security profile

You can also add a team. After adding the user or team, you need to define the field permission. Click the Field Permission link. You will see only the columns with the Column Security flag enabled in its field settings. If you don’t see any columns, go to a table and choose the Column setting and then enable Column Security.

In the field list, double-click the column. In the small popup, define the permissions. Select No for all the options. Figure 8-60 shows the process of choosing permissions for the field.

A window with row entry labeled actual value, actual revenue is boxed. Atop is a dialog box titled Edit Field Security has three rows with dropdown boxes with no option selected, labeled allow read, allow update, and allow create.

Figure 8-60

Choosing permissions for the field

Now click OK and save and close. When Rajeeb opens an opportunity record, he will not be able to see the value of the actual revenue.

Configure Workflows and Concepts

Workflows are components by which you can automate manual tasks. You can automate the following actions using workflows:
  • Creating new records

  • Updating existing records

  • Sending email

  • Calling custom workflows

  • Calling custom actions

  • Using conditions

These workflows are classic CRM workflows that can be used to automate Dynamics 365 CE business needs. You can replace the classic workflows with Power Automate modern flows, which gives you more scope in automating diversified cloud apps, including Dynamics 365 CE. Since many businesses are still using the classic workflow, you should have knowledge about this classic approach.

You can configure real-time or background workflows as needed. Real-time workflows are executed in the same transaction with the core operation. For example, if you want to run a real-time workflow when creating an account, the process of Create Account will not be completed until the real-time workflow execution is complete.

If the workflow runs in the background, the account will be created successfully. After a period of time, when the server is free, the background workflow or asynchronous workflow instance will start execution, without depending on the account creation process.

In real-time workflows, you can choose to run it before or after a value change, but in the background workflow, there is no before option. It will take only the updated value.

You can first define a trigger that will initiate the workflow. The trigger can be event based or on-demand by the user to manually run. Choose the scope as needed. The organization scope will ensure that the workflow will run on all records of the entity type.

Create a Background Workflow

Use the following section to create a background workflow.

Define Basic Info About the Workflow

Open the Power Apps solution. Click Add New Component and choose Automation ➤ Process ➤ Workflow. Figure 8-61 shows the process of adding a classic workflow inside a Power Apps solution.

A window box of Power Apps has options under the context menu, boxed and numbered. From the top, going right, Box number 1 is new, followed by Automation, which is box number 2, then Process, box number 3, and Workflow, which is box number 4.

Figure 8-61

Adding a classic workflow inside the Power Apps solution

Provide a display name and choose a table for which you are configuring the workflow. Enable the Background Run checkbox if you want to run it in the background. For this example, the background is enabled. Say you want to create a task record that’s due three days after the account is created to follow up with the account. Figure 8-62 shows the configuring workflow.

A dialog box titled New workflow has a text box of display name labeled create a task on account create, and has a dropdown box of a table with the account option selected. Below is a ticked checkbox labeled run workflow in the background, then two options, where blank is selected.

Figure 8-62

Configuring the workflow

Click Create. This will open the Workflow Designer. You can set the Scope to Organization, and the Trigger to Record. Figure 8-63 shows the process of adding steps and selecting triggers.

A window under information has a menu bar at the top, followed by a navigation pane on the left with categories common and process sessions. On the right side is a checklist in 5 rows, boxed labeled as triggers. On the bottom part, under add step option are boxed row labels, labeled as action steps.

Figure 8-63

Adding steps and selecting triggers

Click Add Step and choose the Create Record step. In the Create Record step, set the Record Type to Task. Figure 8-64 shows adding the Create New Record step and properties.

A window has a segment with a column with options labeled add step, insert, and delete this step. Below is a text box labeled with create task, followed by a dropdown box of create with option task selected. The dropdown box has a command button labeled set properties on the right.

Figure 8-64

Adding the create new record step and properties

Click Set Properties to specify the task record field values such as Task Subject, Description, and so on. You can specify static values or use the Form Assistance panel to use dynamic values related to the entity for which the workflow was defined. Figure 8-65 shows this process.

A window under create task has a menu bar at the top, followed by boxed text boxes with labels task discuss with account manager for follow up, task discuss with account manager for follow up, account, and a box on the right names form assistant that has text and dropdown boxes that points to text box labeled 3 days after created on the account.

Figure 8-65

Set property of the Create New Record of Type Task

The Regarding field is automatically assigned to Account. For Due date, you want to specify three days after the Account Created On date, so use the form assistance to assign the value. Now save and close.

You have successfully created the workflow. Save and activate the workflow to test it.

Follow these steps to test the workflow as per Figure 8-66, which shows these steps.
  1. 1.

    Open the Sales Hub app and create an account record.

     
  2. 2.

    Navigate to the Activities tab.

     
  3. 3.

    Click Open Activity Associated View.

     
  4. 4.

    You will see the task record.

     

A window with texts and labels boxed and numbered. From the top, going right, Box number 1 is account, followed by Activities, which is box number 2, then Open Activity Associated View, box number 3, and Task Discuss with Account manager for follow-up, which is box number 4. On the bottom right corner, label 5.22.2022, 2.16 P M is boxed.

Figure 8-66

Testing the workflow

If you want to check the status of a background workflow, you can go to advanced settings in the System Jobs area. Filter workflows by entity and you will see the workflow instance status. Figure 8-67 shows the process of checking the workflow instance in a system job.

A window of Dynamics of 365 under settings has a table that has six columns and a row. The column headers are system job, system job name, regarding, status reason, owner, and started on. Row entries workflow, create a task on account create, M S F T account, and succeeded are boxed.

Figure 8-67

Checking the workflow instance in a system job

You can also create real-time workflows using this same process. In later chapters, you learn how to call custom workflow activities from background and real-time workflows.

Configure Custom Actions

You can extend the functionality of Dynamics 365 Customer Engagement by creating custom messages, known as actions. These actions will have associated request/response classes and a Web API action will be generated. Actions are typically used to add new domain-specific functionality to the organization’s web service or to combine multiple organization web service message requests into a single request. For example, in a support call center, you may want to combine the Create, Assign, and Setstate messages into a single new message, called Escalate.

The business logic of a custom action is implemented using a workflow. When you create a custom action, the associated real-time workflow is automatically registered to execute in stage 30 (core operation) of the execution pipeline. In the next chapter, you learn more about the execution pipeline.

You can create custom actions that are specific to an entity or that are global (not specific to any entity). You can call plugins against the custom action in the pre-operation or post-operation stage. You learn more about these stages in later chapters. You can also define input and output parameters inside custom actions.

Create a Custom Action

Let’s consider a business scenario in this section. This example invokes a custom action to request the manager’s approval when a discount for a particular opportunity exceeds 50%.

Open the Power Apps solution and add a new component called Action by selecting Automation ➤ Process ➤ Action. Figure 8-68 shows this process.

A window of Power Apps has a navigation pane on the left, followed by three context menus on the right, with row entry action boxed.

Figure 8-68

Adding an action to the solution

Specify a name and select the Opportunity table. Click Create. Figure 8-69 shows this configuring action.

A dialog box titled new action, from the top has a text box of display name labeled with send approval email for opportunity, followed by options table and none, where option table is selected, then a dropdown box of a table with option opportunity selected. Below, are options labeled blank and template, where blank is selected.

Figure 8-69

Configuring action

This will open the Action Designer window. Add a new input argument of type string called Special Notes. Figure 8-70 shows the input arguments in action.

A window under information has a navigation pane on the left side, where information is selected. On the right, under the general section are text boxes with details to fill out. On the bottom part, a segment of a window box is boxed, labeled input parameters.

Figure 8-70

Input arguments in action

In the Action panel, add a new step and choose Send Email. In the Send Email step, click Set Properties and use the form assistance to assign dynamic values to the respective fields. Figure 8-71 shows sending the email configuration in action.

A window under send email. Below are text boxes to fill out, which are from, to, C cm B c c, and subject. On the right, a box on the right column labeled form assistant with text and dropdown boxes filled out points to a body of an email on the text box on text box on the bottom left side.

Figure 8-71

Sending email configuration in action

Click Save and close. Activate the action. Now you can call the custom action from a workflow. Custom actions don’t run independently.

Create a workflow named Send Approval and configure the trigger as a record field change. Select the field opportunity discount. Add a new step called Perform Action and select the action you created in the previous step. Figure 8-72 shows this process.

A window has the lower part boxed that has a text box and two dropdown boxes. It points to a table on the web page atop that has row entries special notes, target, slingle line of text, lookup, required, V I P customer, and opportunity. Above is a checklist with command button select, boxed.

Figure 8-72

Assigning an input argument value

To test this workflow and action, open an opportunity, change the opportunity discount to more than 50, and save it. The workflow will trigger and the action will call, which will send an email.

Configure Reports in Power Apps

Reports are well researched, planned, and organized documents that are written for a purpose. Strategic-level personals need reports to redefine proper business strategy. You can create Dynamics 365 Power Apps reports by selecting the correct data items from one or more entities, as needed.

Use the following steps to configure a report for accounts.

Step 1: Add a Report Component to the Solution

Open the Power Apps solution and click Add New Component. Choose Report. Figure 8-73 shows the process of adding reports to the solution.

A window has a navigation pane on the left side, where row labeled objects is selected. On the right side, it has a box with 10 row labels, where all is selected, followed by a context menu on the right where a column on the menu bar labeled new is boxed, together with boxed row label report from the context menu.

Figure 8-73

Adding a report to a solution

This will open a new window where you can design your reports. Click the Report Wizard to open it. Figure 8-74 shows the Report Wizard.

A dialog box of report, the new report. Under general section, it has a row label named source that has a text box of report type labeled report wizard report, followed by a command button labeled report wizard below. Below the source row is row label details.

Figure 8-74

The Report Wizard

Click the Start a New Report radio button and then click Next. Figure 8-75 shows the Report Wizard option to choose a new or existing report.

A dialog box is titled get started. It has a row label named select the starting point for your report that has two bulleted selections, where start a new report option is selected. On the bottom right part are three command buttons in a row, which are back, next, and cancel.

Figure 8-75

The Report Wizard option to choose a new or existing report

Step 2: Configure the Report

Specify the report name, a description, and the primary record type. Then click Next. Figure 8-76 shows the report properties.

A dialog box is titled report properties. It has two row labels named specify the name and description of the report, which has two text boxes and specify the record types to include in this report, which has two dropdown boxes. On the bottom right part are three command buttons in a row, which are back, next, and cancel.

Figure 8-76

Report properties

Step 3: Configure the Criteria

Configure the report criteria using the Report Filtering criteria. Figure 8-77 shows the filter condition.

A dialog box is titled select records to include in the report. It has a box named report filtering criteria. The box has text boxes inside labeled all accounts, active, and select. On the bottom right part are three command buttons in a row, which are back, next, and cancel.

Figure 8-77

Filter condition

Step 4: Configure the Layout Fields and Use Grouping

You can configure fields to display on the report and use grouping. Figure 8-78 shows this process.

A dialog box is titled select records to include in the report. It has a box named report filtering criteria. The box has text boxes inside labeled all accounts, active, and select. On the bottom right part are three command buttons in a row, which are back, next, and cancel.

Figure 8-78

Configure the layout

Step 5: Configure the Report Format

You can configure the report format using tables only or using charts and tables. If your data contains numeric fields, it’s best to use the charts and tables format. Figure 8-79 shows this process.

A dialog box is titled format report. It has two selections in rows labeled table only, and chart and table. Table only is selected. On the bottom right part are three command buttons in a row, which are back, next, and cancel.

Figure 8-79

Choosing the report format

Finally, click Next in the report summary. Figure 8-80 shows the summary of the report.

A dialog box is titled report summary. It has row labels report name, which is account report, report description, which is accounts report, and primary record type, which is accounts. On the bottom right part are three command buttons in a row, which are back, next, and cancel.

Figure 8-80

Report summary

Next click Finish. Your report will be successfully created. Click Run Report to render the report.

The report is rendered as per your configuration. You can run the report from entity view in model-driven apps. Figure 8-81 shows the rendered report.

A window of Power Apps under Report, Accounts Report. On the menu bar at the top, label run report is boxed. Atop is a window box of a boxed table that has three headers, where the second header, account name has 14 row labels.

Figure 8-81

Rendered report

Install Multiple Languages in Environments

Dynamics 365 supports multiple languages. To install multiple languages, navigate to the advanced settings and click the System Settings. Figure 8-82 shows the Administration option.

A window of Dynamics 365 under the settings section. It has 3 column headers, which are business with 3 row labels, customization with 3 row labels, and system with 3 row labels. Administration, under column system is boxed.

Figure 8-82

The Administration option

Choose Languages. Select the desired languages and click Apply. Figure 8-83 shows the language settings.

A window of Administration has row label Languages boxed. Atop is a dialog box of language settings with a table that has three columns and four rows. The column headers are language, language code, and status. The row entries under language, which are Greek, Hebrew, and Hindi are boxed. On the bottom right part, command button apply is boxed.

Figure 8-83

The language settings

It will take some time to install all the selected language packs. After the packs are installed, you can navigate to the personalization settings. In the Languages section, you can select your language and click OK. This will change your User Interface language to the desired language. Figure 8-84 shows the Language Change options.

A dialog box titled Set Personal Options has a text box, filled with English as the base language, and two dropdown boxes, where both Greek are selected. On the bottom part are the two command buttons O K and Cancel.

Figure 8-84

Language Change options

As an example, this will change the UI’s language to Greek. Figure 8-85 shows the language change process in action.

A window of Dynamics 365. On the left is a navigation pane with texts written in Greek. The third to fifth row labels are boxed. On the right, the first option on the menu bar written in Greek is boxed.

Figure 8-85

The language change in action

All the sections are not updated yet to Greek, so you’ll need to update the translations.

Working with Translations

When you upload translations, you need to export them from the Power Apps solution. Open the Power Apps solution and add the necessary components that require translation.

Select Solution Overview. Click the Export Translation command to export the translation template. For more details, see https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/customize/export-customized-entity-field-text-translation?view=op-9-1.

Figure 8-86 shows the export translation process.

A window of Power Apps. On the left is a navigation pane, where the third-row label, overview, is selected. It has an arrow line that points to translations option on the menu bar, together with export translation, boxed.

Figure 8-86

The export translation process

Export Translation will prompt you to download the file so that you can open it and define specific translations of English words.

Extract the ZIP file and open CrmTranslations.xml using Microsoft Excel. Figure 8-87 shows the Extract Translation package

A window has a label on the address bar that reads C r m Translations, underscore, School Management Solution, underscore, 1, underscore, 0, underscore, 0, underscore, 0. It has two text files, which are content types and C r m translations.

Figure 8-87

Extract Translation package

In the Display strings, you will see the English and corresponding Greek translations. Figure 8-88 shows this process.

A table in an Excel worksheet has 4 columns and 37 rows. The column headers are entity name, display string key, 1033, and 1032. On the bottom part, the second sheet titled display strings, boxed. Under columns C and D are rows 1 to 15, boxed.

Figure 8-88

Updating the corresponding language translations

But for the Localized Label, some English words don’t have Greek translations. Open that sheet and update the corresponding Greek words to English ones. Figure 8-89 shows the Update Corresponding Language Translation in the Localized Labels.

A table in an Excel worksheet has 5 columns and 37 rows. The column headers are entity name, object I D, object column name, 1033, and 1032. On the bottom part, the third sheet titled localized labels, boxed, has an arrow line that points to a label that reads student, with a greek text at Columns D and E, on row 27.

Figure 8-89

Update the corresponding language translation in the Localized labels

After all these changes are done, sav the file and ZIP it. Import the translation. Refresh the screen; you will see the new translations.

Working with a Document Template

You can use Word or Excel to generate documents that contain values from records in Dynamics 365. To create a template, follow these steps.

Step 1: Download a Template

Go to the advanced settings and click Templates. Choose Document Templates. Figure 8-90 shows the Document Templates option.

A window titled Dynamics 365 has the templates section. Under the section, it has 5 templates, which are article templates, emails templates, and email signatures on Column 1, and contract templates and document templates, which is boxed on Column 2.

Figure 8-90

Document Templates option

Click +New. Choose Word Template and filter the results by the Quote entity. Figure 8-91 shows the download template.

A dialog box is titled Create template from Dynamics. From the top, it has boxes in a column named Excel template and Word template, followed by a dropdown menu where quote is selected. On the bottom right corner are command buttons upload and select entity.

Figure 8-91

The download template

Click Select Entity. Choose 1: N Relationship Quote Line Details and download the template. Figure 8-92 shows the select entities.

A window titled select entity has 3 columns of boxes. Box 1, 1.N Relationship has a checklist of entity names in rows, where quote line detail is checked. Box 2, N.1 Relationship has checkboxes in 8 rows. Box 3, N.N Relationship has a checkbox named contact. On the bottom right corner is a command button labeled download template.

Figure 8-92

Select entities

Step 2: Edit the Template Using Developer Mode

Open the downloaded template in Microsoft Word. Go to the Developer tab. If the Developer tab is not visible, go to File ➤ Options and select Customize Ribbon. Then enable the Developer option and click OK. Figure 8-93 shows the process of enabling the Developer option.

A dialog box titled word option. On the left, a box has a row named customize ribbon selected. On the right, it has a box that has 2 dropdown menus with popular commands and main tabs selected. Under the main tabs is a checklist, with a developer checkbox with row labels, boxed. On the bottom are command buttons O K which is boxed, and cancel.

Figure 8-93

Enabling the Developer option

In the Word document, design the template as needed, such as adding headers and footers, and so on. After that, select the Developer tab and Click XML Mapping. In the right panel, choose the Quote option. Figure 8-94 shows the use of the XML mapping option.

A window of a Word file is on the Developer menu, with the X M L mapping on the ribbon boxed. On the right, the navigation pane named X M L Mapping has a text box that is boxed labeled u r n, colon, microsoft-c r m, slash document-template, slash, quote, slash 1084, slash.

Figure 8-94

Using the XML mapping option

You can insert dynamic values into the template using XML mapping fields. Figure 8-95 shows the process of adding fields to the document from mapping.

A window has a page with a header Quote. Below, a text that reads customer I D name is boxed with an arrow line that points to a boxed context menu with insert content control, and plain text selected in the navigation pane on the right. On the right navigation pane, it has a header named quote, boxed.

Figure 8-95

Adding the fields to a document from mapping

After the dynamic values are prepared, you can upload the final template. Rename the Word template My Custom Quote Template.

Step 3: Upload the Template

From the advanced settings, choose ➤Templates ➤ Document Templates. Then choose Upload Template and select the document you just prepared. Figure 8-96 shows the process of uploading a document template.

A dialog box titled upload template. At the center, it has a box with an icon of a cloud with an arrow that points upward and texts that read drag a file here or browse to upload a file. Below is the file name, which is My Custom Quote Template dot d o c x. On the bottom right corner, there are command buttons upload and cancel.

Figure 8-96

Uploading a document template

Step 4: Generate the Template

Once the template is uploaded, you can generate this document in a quote entity record. Open a quote and click Export to PDF. Figure 8-97 shows the Export to PDF option.

A segment of a window has column labels, check access and export to P D F.

Figure 8-97

Export to PDF option

Choose the template you uploaded. You will see that the fields are dynamically generated. Figure 8-98 shows the Export to PDF option, which renders a PDF.

A window has export to P D F option from the menu bar boxed. Atop is a new window box titled Export to P D F. On the right, it has a navigation pane where my custom quote template is boxed and selected. It has an arrow line that points to a P D F page on the right named Quote, with details below.

Figure 8-98

The Export to PDF option renders a PDF

Now you can download or send emails with attachments.

Summary

In this chapter, you learned about the following concepts:
  • Admin Centers and their uses

  • Importing data into Power Apps

  • Configuring duplicate detection rules

  • Configuring the auditing feature in Power Apps

  • Adding users to environments

  • Using the security matrix and configurations

  • Configuring workflows and concepts

  • Configuring custom actions

  • Configuring reports in Power Apps

  • Working with email templates and signatures

  • Installing multiple languages in environments

  • Working with translation

  • Working with document templates

In the next chapter, you will learn about the following:
  • Working with client-side JavaScript in Power Apps

  • Developing plugins for Power Apps

  • Developing custom workflow activities in Power Apps

  • Editing command bars in Power Apps

  • Business scenarios and implementations

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
3.138.102.114