Custom Table System Default Views in Power Apps

System Default Views for Custom Table in Power Apps

Prev Question Next Question

Question

You create a custom model-driven app.

The app contains the views for a custom table.

What types of system default views does Power Apps create for a custom table?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D. E. F.

Correct Answers: A, B, D and F

Power Platform model-driven app provides the three types of views: Personal - created by the user and visible to the user and shared people.

System - special views created for system tables or automatically for the custom tables.

Public - general-purpose views that are visible to all users.

The System views include the following views for the tables: Quick Find - a default view for the results from the Quick Find operation.

Advanced Find - a default view for the results from the Advanced Find operation.

Associated - a default view for the Related tables.

Lookup - a default view for a search in a lookup field.

The organization owns the system view, and everybody can see them in the Power Apps portal.

The system view has the following name convention: the table name plus Advanced Find View, or Associated View, or Lookup View, like Customer Advanced Find View or Customer Associated View (Number 1)

The Quick Find view uses the table name in the plural - Quick Find Active Customers (Number 2)

By default, there are two public views for every table: Active and Inactive.

These views include the tables' plural names, such as Active Customers (Number 3) and Inactive Customers (Number 4)

You can also create a Public view using the "Add view" button (Number 5), like New Shiny View (Number 6).

Power Platform / {{webapiurl}}/EntityDefinitions(LogicalName='account')/Attributes(LogicalName='emailaddress1') GET vy {{webapiurl}}/EntityDefinitions(LogicalName='account')/Attributes(LogicalName='emailaddress1') Headers (13) Body @ Pre-request Script Tests Settings Current Token OAuth 2.0 a This access token is only available to you. Sync t! The authorization data will be automa_ Inherit auth from parent Access Token the request. Learn more about autho Add authorization data to API Key Bearer Token Header Prefix © Basic Auth i Y Configure New Token Digest Auth OAuth 1.0 Token Name OAuth 2.0 Grant Type Hawk Authentication AWS Signature Callback URL © NTLM Authentication [Beta] Akamai EdgeGrid Auth URL © Client ID @ Scope © State @ Client Authentication Clear cookies © Get New Access Token he token to let collaborators on this request use it. Available Tokens eyJOeXAIOIJKVIQiILCJhbGciOiJSUZIINi Bearer CBPostman Implicit {{callback}} O Authorize using browser {{authurl}} {{clientid}} e.g. read:org State Send as Basic Auth header

You cannot delete the System views or see them in model-driven apps as the system views.

Instead, you see the Public views as system views (Number 1)

You can create your personal view in an app using the "Create view" button (Number 3)

After that, you will see the view in the app's screen view dropdown under the "My Views" section (Number 2)

But you will not see it on the Views tab in the Power Apps portal.

Power Platform / {{webapiurl}}/EntityDefinitions(LogicalName='account’)/Attributes(LogicalName='emailaddress1') 000 GC #8 A GET v {{webapiurl}}/EntityDefinitians(LogicalName='account’)/Attributes(LogicalName='emailaddress1') A Headers (12) KEY VALUE DESCRIPTION eco §=6 Bulk Edit Presets v Params Authorization Body @ Pre-request Script Tests Settings Cookies > Headers © 10 hidden application/json ka Prefer odata.include-annotations="*" Key Value Description

All other options are incorrect.

For more information about model-driven app views, please visit the below URLs:

When you create a custom model-driven app in Power Apps, it automatically generates several system views for each entity (table) that is added to the app.

The types of system default views that are created for a custom table are:

  1. Associated View: This view displays a list of records that are associated with the current record in a relationship. For example, if you have a custom entity called "Orders" and another entity called "Order Lines," the associated view for the "Orders" entity would show a list of all the order lines associated with each order.

  2. Quick Find View: This view allows users to search for records in the table using a search bar. The search looks for matches in all the fields that are searchable in the table.

  3. Inactive View: This view shows all the records that have been deactivated (i.e., set to inactive status). Inactive records are not visible in other views, such as the default "Active" view.

  4. Advanced Find View: This view allows users to create complex queries to search for records based on multiple criteria.

  5. Lookup View: This view displays a list of records that can be selected as a lookup value for a field on another entity.

  6. Admin View: This view is only visible to users with administrative privileges and shows all the records in the table, regardless of their status (active or inactive).

Overall, these default views provide a useful starting point for users to view, search, and manage records in the custom table within the app.

Prev Question Next Question