You are developing a Fleet management module for Microsoft Dynamics 365 Finance and Operations. You create an FMVehicle table to store information that is specific to each vehicle in your fleet…

Question

Options

• AWorkspace Operational
• BList Page
• CDialog - Basic
• DDetails Master

• A
  6% (1)
• B
  6% (1)
• C
  12% (2)
• D
  76% (13)

Explanation

Operational workspace: This is the standard pattern currently used forworkspace development. Becauseof the set of components that are permitted in it, this pattern has superiorperformance over the deprecated"workspace" pattern. For this reason and to ensure visual and behavioral consistency with the otherworkspaces in the system, we recommend that you use this pattern. List Page: A list page presents a set of data on a user interface that is optimized so that you can browserecords, find the right record, and then take an action upon that record. Thelist page lets the user search,filter, and sort the data. FactBoxes on the right side of the grid show related data for the active record. Actions that are relevant to the record are located on the ActionPane at the top of the page. The use of thispattern is now discouraged when there is a 1:1 correspondence between the List Page and Details page. Current guidance is to use this pattern only in other situations, such aswhen list pages have no backingdetails pages or have multiple backing details page (for example, when project quotations and salesquotations are shown together in the same List Page). Detail Master: A details form is the primary method for entering data. Theseforms let the user view, edit,and act upon data. All content on these form types is structured into FastTabs that can be expanded andcollapsed, so that multiple FastTabs can be open at the same time. The FastTabs can contain fields or agrid, and each FastTab can have a local toolbar. This is the basic Detail Master pattern. This is the patternthat you should use by default.

No community discussion yet for this question.