Question
You are modifying a model-driven app for a bicycle company.
The app modifications must meet the following requirements:
- The order form must include a column that calculates payments based on how many years the customer wants to finance a bicycle.
- A pop-up box must remind the employee to validate the information entered before saving.
You must use out-of-the-box features before customizing the application.
What should you do? To answer, drag the appropriate actions to the correct requirements. Each action may be used once, more than once, or not at all.
Explanation
Calculate payments: configure an out-of-box feature. A calculated or formula column computes the payment from the price and the number of financing years without any code, so the built-in feature meets the requirement. A pop-up box must appear: customize the app. No built-in, no-code feature opens a dialog before saving. Business rules can only set or clear values, set defaults, show an error message on a column, change requirement level, show or hide and enable or disable columns, or add a recommendation, and none of these is a pop-up box. A reminder dialog therefore needs client script, for example an OnSave event handler that calls Xrm.Navigation.openConfirmDialog. Editing XML is not needed for either requirement.
