- ABeing a system administrator and Processing deposits
- BCanceling a payment
- CManaging system security
- DBoth B & C
Time Taken:
Correct Answer:
Wrong Answer:
Percentage: %
Justification:
Related Lesson: Security Architecture Overview
Public and protected methods that are marked as final can't be wrapped in extension classes. You can override this restriction by using the Wrappable attribute and setting the attribute parameter to true ([Wrappable(true)]). Similarly, to override the default capability for (non-final) public or protected methods, you can mark those methods as non-wrappable ([Wrappable(false)]).
The Wrappable(true) attribute can be used to override the restriction and allow final methods to be wrapped in extension classes. Hookable(true) does not influence chain of command wrapping. Wrappable(false) marks methods as non-wrappable. Hookable(false) makes the method unable to be wrapped in an extension class.
Implement Chain of Command - Training | Microsoft Learn
class AnyClass2 { [Wrappable(false)] public void doSomething(str message) {...} [Wrappable(true)] final public void doSomethingElse(str message) {...} }
Extension classes are final classes that are adorned with the ExtensionOf attribute and that also have a name that has the _Extension suffix.
Because the classes are instantiated by the runtime system, it's not meaningful to derive from the extension class. Therefore, the extension class must be marked as final.
Reference:
https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/extensibility/method-wrapping-coc
Step 1:Open the customer form and apply filters to the grid.
To add a list to a workspace, first sort or filter the list on the page so that it shows the information as you want it to appear in the workspace.
Step2:Select the Options actions pane tab and then select Add to workspace
step3: Select Workspace and Presentation options
Step 4: Select Configure -
After you select Configure, a dialog box appears, where you can select the columns that should appear in the list in the workspace.
Example of Restricted -
Suppose we have two tables (Customer & Order) and the relation is of One-To-Many i.e Customer can have many orders.
So on a parent table i.e.(Customer) if I set a delete action property to RESTRICTED for Order table. Then If I go and delete the record from a Customer table. It will first check the record in the child table and if exist that warning prompt saying that first we need to delete a record from child table.
Incorrect Answers:
B: Example of Cascade:
Suppose we have two tables (Customer & Order) and the relation is of One-To-Many i.e. Customer can have many orders.
So on a parent table i.e.(Customer) if I set a delete action property to CASCADE for Order table. Then If I go and delete the record from a Customer table. It will also delete all the related records in Order table automatically.
C: Example of Cascade + Restricted
Suppose we have three tables (Person ,Customer & Order) Now Person is a parent of Customer table, and Customer is a parent of Order table having (One-To-
Many) relations -
If I set a Delete action property on Person table to CASCADE for customer table and If I set a Delete Action property on a CUSTOMER table for Order table to
CASCADE +RESTRICTED.
So if I delete a record from Customer table then It will first check the record in the child table(order table) and if exist that warning prompt saying that first we need to delete a record from child table.
But if I delete a record from Person table it will automatically delete a record in Customer table and all records related to customer table in Order table would also be deleted.
No". The Simple List pattern doesn't have a slot for adding a tab, and trying to add a tab control will cause the form to no longer be compliant with the Simple List pattern, even though it still compiles.
See documentation "The vertical arrangement of tabs implies the order of completion
Pattern have vertical tabs.
AB: Environment monitoring is a simple way to access current activity on environments in your Finance and Operations apps implementation. By using the
Environment Monitoring and SQL Insights that come in a user-friendly dashboard, you can see measurements and diagnostics of your environment's health.
Within the Health metrics dashboard, some issues are reported directly to the Microsoft Service Engineering Team and some are mitigated immediately. If there are any concerns regarding performance, this is a good way to gain insight into potential issues.
All SQL performance tools in LCS are available under the SQL Insights tab on the Environment Monitoring page for a specific environment.
Reference:
https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/lifecycle-services/performancetroubleshooting
https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/lifecycle-services/performancetroubleshooting