You create a new custom table Invoice in a model-driven app.

The correct answer is B. Active Invoices D. Inactive Invoices. When you create a new custom table (e.g., 'Invoice') in a model-driven app via Dataverse, the platform automatically generates a set of default system views. The two primary ones created for every new table are Active Invoices (B) - a view showing all records in an active state…

Configure Microsoft Dataverse

Question

You create a new custom table Invoice in a model-driven app.

Exhibit

Options

AQuick Find Active Invoices
BActive Invoices
CInvoice Lockup View
DInactive Invoices
EInvoice Advanced Find View

How the community answered

(36 responses)

A
3% (1)
B
94% (34)
C
3% (1)

Explanation

When you create a new custom table (e.g., 'Invoice') in a model-driven app via Dataverse, the platform automatically generates a set of default system views. The two primary ones created for every new table are Active Invoices (B) - a view showing all records in an active state - and Inactive Invoices (D) - a view showing all deactivated/inactive records. While other views such as Quick Find and Advanced Find views are also auto-generated, the question targets the two foundational status-based views that Dataverse creates by default for every new table. The 'Invoice Lookup View' (C) naming convention is not a default auto-created view name.

Topics

#Dataverse tables#Model-driven app views#Default views#Table creation

Community Discussion

No community discussion yet for this question.

Full PL-200 Practice