Model Driven Apps Flashcards

1
Q

Benefits of Model Driven Apps

A

1) Rich component-focused no-code design environments
2) Create complex responsive apps with a similar UI across a variety of devices from desktop to mobile
3) Rich design capability
4) Your app can be distributed as a solution

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

System Business Process Flows

A

1) Lead to Opportunity Sales Process
2) Opportunity Sales Process
3) Phone to Case Process

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Conditions to run BPF in offline mode.

A

1) The business process flow is used from a Power Apps app
2) The Power Apps app is enabled for offline use.
3) he business process flow has a single entity.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Commands available for BPF in offline mode

A

1) Next stage
2) Previous stage
3) Set Active Stage

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Building blocks of Model Driven App

A
Data
1) Table/Entity
2) Column/Field
3) Relationships
4) Choice Option Set
UI
1) App
2) SiteMap
3) Forms
4) Views
Logic
1) BPF
2) Business Rules ( business rules do not work on multi-select choice, A business rule may also not execute because a column referenced in the business rule is a composite column eg fullname)
3) Workflows
4) Actions
5) Power Automate/Flow
Visualization
1) Charts
2) Dashboards
3) Embedded Power BI - tiles and dashboards
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Requires the configuration of the Data Integrator to make your business data available within Common Data Service

A

1) Dynamics 365 Finance,
2) Dynamic 365 Supply Chain Management and
3) Dynamics 365 Retail currently

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Can’t find entity while creating a BPF on step select Common Data Service Entity

A

make sure the “Business process flows (fields will be created) is set for the entity in the entity definition.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Minimap on BPF

A

1) lets you see the whole process

2) quickly go to a part of the process.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Add workflow to the BPF

A

Workflow should be on-demand active workflow

1) to specific stage -
* if the workflow should be triggered when the process enters or exits the stage.
* The workflow component must be based on the same primary entity as the stage.
2) Global workflow item -
* if the workflow should be triggered when the process is activated or archived (ie status changes to Completed or Abandoned).
* The workflow component must be based on the same primary entity as the process.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Security roles for BPF

A

By default, the System Administrator and System Customizer security roles have access to new BPF. Rest we need to give explicit access.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Snapshot of BPF

A

To take a snapshot of everything in the business process flow designer, select Snapshot on the action bar. This option is useful if you want to share and get comments about the process from a team member.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Set Process Flow Order in BPF

A

If you have more than one business process flow for an entity (record type), you must specify which process is automatically assigned to new records. On the action bar, select Order Process Flow. For new records or records that don’t already have a process flow associated with them, the first business process flow to which a user has access will be used.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Branching in BPF

A

Branching rules must be based on the steps in the stage that immediately precedes them.

You can combine multiple conditions in a rule by using the AND operator or the OR operator, but not both.

When branches are merged, either all the peer branches must be merged to a single stage, or each peer branch must end the process. A peer branch can’t merge with other branches and end the process at the same time.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Varieties of BPF

A

1) Embedded within a model-driven app
2) Immersive BPF - Stand-alone solution

Embedded

1) are visual representations of a series of work steps within an end-to-end process.
2) They always appear along the top of a model-driven app in their own control.
3) a component within the larger model-driven app

Immersive

1) Can exist on its own, and its built entirely within the Power Automate editor.
2) They will always exist within the default solution in an instance of CDS and are only accessible within Power Automate or the data tab that is associated with an entity in CDS.
3) simplified creation and streamlined management.
4) standalone solution.

A user always views and completes an embedded BPF within a model-driven app. An immersive BPF is a stand-alone app, and it is built solely for the purpose of completing the business process.
The immersive BPF exists as a the entire solution rather than a component of a larger model-driven app.
The main difference is how they are launched and the context that they are viewed in.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Steps to create Immersive BPF

A

1) Select None(Immersive Business Process) under entit drop-down list while creating the BPF.
2) New entity gets created automatically.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Form Event handlers

A

1) Form - OnLoad, OnSave
2) Tab - TabStateChange
3) Field -OnChange
4) IFrame - OnReadyStateComplete
Each element can have upto 50 separate event handlers configured.

17
Q

Multiple forms

A

1) Can create more than 1 Quick Create form for an entity, but only the first one in order will be available for end users.

18
Q

Charts available in model driven app

A

1) Column
2) Area
3) Bar
4) Line
5)Pie
6)Funnel
7)Tag
8) Donut
CABLPFTD

19
Q

Editable subgrid

A

Editable grids support:

1) In-line editing of rows at the table or sub-grid level (includes custom tables)
2) System views and personal views
3) Web and mobile clients
4) Navigation with a keyboard or mouse
5) Grouping and sorting (you can group by/sort rows on the client-side by any column in the current view)
6) Filtering
7) Moving and resizing columns
8) Pagination
9) Saving changes from one session to another for grouping, sorting, filtering, pagination, and moving and resizing columns
10) Lookup configuration
11) Calculated columns and rollup columns
12) Business rules (Show error message, Set column value, Set business required, Set default value, Lock or unlock column)
13) JavaScript events
14) Enabling or disabling of cells based on security role
15) Users can continue to use search and charts, and can access the action bar as with read-only grids

Note -
Group by views
* work on client side only
* works only on one page of data.
* does not show you all options based on your complete data set on the server
* shows grouping only on the current page

20
Q

Nested grid

A

Nested grids are only available for phones and tablets, not the web.

21
Q

Editable grid within subgrid

A

To save an editable grid change within a sub-grid, the user must explicitly save before navigating out of the form.

1) Open solution explorer.
2) Open the form that contains the sub-grid.
3) Select the appropriate control, and then select Change Properties on the ribbon.
4) In the Set Properties dialog box, select Controls, select Add Control, and then follow the same steps as followed for editable subgrid on entity

22
Q

Data types that aren’t editable in an editable grid

A

1) Customer and Partylist Lookup columns;
2) Composite (address) columns;
3) State/Status columns;
4) Lookup table-related columns (for example, the Account table includes a contact lookup, where the Contact column is editable but the EmailAddress(Contact) column is not editable).

23
Q

Business rules on editable grids

A
  • Business rules work only if conditional column is a column on the grid.
  • If the column is not a column the business rules won’t work.
  • Verify that each column referenced in the business rule is also included on the form.
  • business rules on an editable grid do not fire if the editable grid is configured on a dashboard.
24
Q

Classic Workflow

A

1) Stages - make the workflow logic easier to read, and explain the workflow logic. However, stages do not affect the logic or behavior of workflows. If a process has stages, all the steps within the process must be contained with a stage.
2) Steps - are a unit of business logic within a workflow. Steps can include conditions, actions, other steps, or a combination of these elements.

25
Q

Datamaps

A

1) Import files can only contain one type of data, such as contacts, leads, accounts, or cases.
2) The column headings in the source file must match exactly with the field names in customer engagement apps.

26
Q

Duplicate detection jobs

A

To maintain the integrity of system data, you should check for duplicates regularly to make sure that users don’t inadvertently create duplicate contacts, accounts, leads, or other types of records.

The Check for Duplicates wizard helps you set up a bulk “job” that finds and cleans up duplicate records. You can schedule the job to run daily, and you can receive an email confirmation when the job finishes.

1) Settings > Data management > Duplicate detection jobs.
2) n the Use Saved View drop-down list, select a view if you want to limit the records searched to records in that view.

27
Q

Duplicate Detection Rules

A

1) Settings > Data management > Duplicate detection rules.
2) Duplicate detection rule criteria
Base Record Type - choose the type of record that this rule applies to for eg Contacts
Matching Record Type - choose the type of record to compare
For example, you might want to compare the Email field in Contacts to the Email field in Leads.
3) If you want the rule to consider only active records while detecting duplicates, select the Exclude inactive matching records check box
4) If you want the rule to be case-sensitive, select the Case-sensitive check box.
5) If you selected different record types for the base and matching record types, for each new criterion, in the Base Record Field column, choose Select, and then choose a field name. In the same row, in the Matching Record Field column, choose Select, and then choose a field name.

  • OR -

If you selected the same record types for the base and matching record types, for each new criterion, in the Field column, choose Select, and then choose a field.

6) In the same row, in the Criteria column, choose Select, and then choose an operator. For example, select Exact Match.
7) If you specified Same First Characters or Same Last Characters, in the No. of Characters column, choose Enter Value, and then enter the number of characters to compare.
8) If you don’t want the rule to consider blank fields (null values) as equal while identifying duplicates, select the Ignore Blank Values check box.
9) The number of criteria that you can select is limited by the number of characters that can be stored in the matchcode for the record. As you add criteria, watch the Current matchcode length value shown at the bottom of the criteria list.
10) When you’re finished adding criteria, choose Save and Close.
11) To make the new or changed duplicate detection rule usable, select the rule, and then choose Publish.

Note - When you publish a duplicate detection rule, a matchcode is created for every record in the matching record type for that rule.

28
Q

How many Duplicate detection rules for same base record type can be published at one point of time?

A

You can publish only 5 rules for the same base record type (Account, for example) at a time.
You might need to delete or unpublish an existing rule if you bump up against this limit.

29
Q

With the Import Data Wizard, you can specify the “Map Automatically” option. The wizard automatically maps all the files and the column headings with record types and fields if:

A

The file names exactly match the display name of the record type.
The column headings of the file you are importing exactly match the display names of the fields in the record.