What MB-820 Questions and Answers feature?

Load the report for users in a specific location: OnInitReport

Validate data before processing: OnPreReport

Define filter based on Department field: OnPreDataItem

The requirements for the report are:

The report must be loaded for users in a specific location only.

Data entered in the request page must be validated before any further processing.

A filter must be defined for users based on the Department field defined in user setup.

Trigger Matching:

The report must be loaded for users in a specific location only.The correct trigger for loading the report is OnInitReport.

This trigger runs when the report is initialized, and you can use it to define user-specific loading conditions, like location-based filtering.

Data entered in the request page must be validated before any further processing.The correct trigger for validation before processing is OnPreReport.

This trigger occurs before the report is run and can be used for data validation before further processing begins.

A filter must be defined for users based on the Department field defined in user setup.The correct trigger to define filters is OnPreDataItem.

This trigger occurs before data item processing begins and is used to apply filters such as those based on the Department field in the user setup.

SharedLayout = true allows for the layout to be shared across views, and it is often used when defining a custom layout that should follow specific filtering conditions.

The Filters property specifies the exact filter criteria for the view, in this case, filtering on Balance > 500 and the Currency Code = LCY (local currency).

A uses incorrect filter syntax and shareLayout = false, which doesn't allow the layout to be shared, so it’s not ideal for this use case.

C and D both have issues with the filter syntax and do not use proper Currency Code filtering or share layout settings.

For more details, check Creating Views in Business Central.

Use the company hardware architecture to run the deployment: On-premises

Use sandbox environments to develop extensions: Online

Allow tenants to connect to Shopify with the standard connector: Online

Use Microsoft Power Automate to create a workflow that calls a business event: Online

When deploying Microsoft Dynamics 365 Business Central, there are two main deployment types to consider: On-premises and Online.

On-premises Deployment:

The requirement to use the company's hardware architecture implies a need for an on-premises deployment. This is because on-premises deployment allows for the application to be installed and run directly from the company's in-house servers and computing infrastructure, giving full control over the environment and data.

Online Deployment:

The use of sandbox environments for developing extensions is a feature provided in the online version of Business Central. Sandbox environments are a part of the service offered in the cloud-based version, which allows developers to test and develop without affecting the live environment.

Connection to Shopify with the standard connector implies an online deployment. The standard connector is typically a cloud-based service that allows Business Central to connect with other cloud platforms like Shopify, which is more seamlessly integrated with the online version.

Lastly, the use of Microsoft Power Automate to create a workflow that calls a business event suggests an online deployment. Power Automate is a cloud-based service designed to create automated workflows between applications and services - which aligns with the services provided by the online version of Business Central.

Therefore, each requirement aligns with the deployment types as indicated above.