DOWNLOAD the newest CramPDF MB-820 PDF dumps from Cloud Storage for free: https://drive.google.com/open?id=1GxErHWOS3b_wYVKJdTPG4Dkg00wxRjTJ
If you are worried that it is not easy to obtain the certification of MB-820. Our MB-820 study questions can meet your needs. Once you use our MB-820 exam materials, you don't have to worry about consuming too much time, because high efficiency is our great advantage. You only need to spend 20 to 30 hours on practicing and consolidating of our MB-820 learning material, you will have a good result. After years of development practice, our MB-820 test torrent is absolutely the best. You will embrace a better future if you choose our MB-820 exam materials.
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
>> MB-820 Latest Exam Pattern <<
Wondering where you can find the perfect materials for the exam? Don't leave your fate depending on thick books about the MB-820 exam. Our authoritative MB-820 study materials are licensed products. Whether newbie or experienced exam candidates you will be eager to have our MB-820 Exam Questions. And they all made huge advancement after using them. Not only that you will get the certification, but also you will have more chances to get higher incomes and better career.
NEW QUESTION # 10
You need to create the Fabrikam Vendor API for the accounting department.
How should you complete the code segment? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Answer:
Explanation:
Explanation:
NEW QUESTION # 11
Case Study 2 - Alpine Ski House
Company Background
Alpine Ski House is a company that owns and operates hotels, restaurants, and stores.
Currently, the company uses the following software and interface:
- Property management software (PMS) to manage hotel rooms
- On-premises accounting software to generate sales invoices and create purchase orders
- An API that allows restaurants and stores to obtain necessary information Restaurants and stores use standalone software for point of sale (POS) devices. Each day, the POS terminals generate a text file of sales data and save the files in a server folder. An account assistant must manually import the files to the current software tables to be processed by the system.
The general manager receives several reports monthly from department managers. The reports take too much time to prepare.
Planned improvements
The company is moving from a different system to Business Central online to manage the whole company.
The company plans to increase efficiency in every department by using APIs to obtain or share information between the different systems.
Each department involved in purchasing must be able to make purchase requests automatically and easily. The departments do not need access to the full ERP management system.
Technical specifications
Alpine Ski House requires the development of several extensions for the planned improvements.
Business Central design patterns must be used to develop all extensions.
Alpine Ski House must develop the following pages:
- Pages that provide multiple configurations in a multistep dialog, like a wizard, to provide required information when the extensions are first installed
- Department-specific Role Center pages to show relevant information and pages with additional information The IT department plans to use Power BI to analyze departmental information. The database must be configured to provide optimal performance.
Department-specific requirements
Housekeeping department
The housekeeping department requires the following to increase efficiency and help avoid data entry errors:
- A Housekeeping Role Center to minimize navigation to relevant areas in Business Central online and to show relevant information in it
- Pages to embed into a new Room page to show additional information about the Room entity
- A table named Room Incident for the housekeeping team to enter room issue information
- A Housekeeping canvas app that connects to an extension
- The department requires the development of an extension with a new API page named RoomsAPI.
- The housekeeping team will use RoomsAPI to publish room details, update when work is complete, or provide repair notifications from the canvas app.
- This custom API page must expose a custom table named Rooms and have an ID 50000. The table must be able to update from the PMS. The PMS team must know the endpoint to connect to the custom API.
- A developer provides the following details for the API page:
- The extension must be published in Business Central online and include a list page named Room List that includes all hotel rooms.
- Installation or updates to this extension must meet the following requirements:
o Some web services must be published automatically.
o The version of the specified application's metadata must be obtained in AL language, o The code required to perform tasks cannot be accessible from other parts of the application.
The Room Incident table information must include the following fields:
- Incident entry: An incremental number
- Room No.: A room from the Room table
- Incident Date: The work date
o The table definition in the Room Incident table must autofill the Incident Date when the housekeeping team inserts a new record, o The value for Incident Date must be the work date configured in the Business Central online client.
- Status: Includes the following options to identify the status of the incident:
o Open: When the Room Incident is created
o In Progress: When someone starts repair work
o Closed: When the incident is solved
- Incident Closing Date: Auto-updating field (when the status passes to Closed, the field will update with the work date)
- Incident Description: Text
- Image: Media data type
o The stored picture must be downloadable from a menu action,
o A Room Incident page must be developed to contain the download action.
Department-specific requirements
Restaurants and stores
- To increase efficiency, the new system must manage the generated data from the restaurants and stores directly by using the API on the POS terminals.
- The company requires a codeunit called from a job queue to read the information from the POS terminal APIs.
- The POS terminal information must be stored in a table named POS Information, have an ID
50100, and be editable on a page.
- The account manager requires an option on the menu of the page to run the process manually.
- To analyze the information received from the POS terminals, the company requires:
- A custom API named ticketAPI to export the information to Power BI
- Use of the Read Scale-Out feature to improve database performance
Department-specific requirements
Purchasing department and non-conformity handling
The purchasing department requires a new entity in Business Central online to log non- conformities of goods received from vendors. The entity must be set up as follows:
- The non-conformity entity must have two tables:
o a header with common information
o one or more lines with the detailed received items that are non-conforming
- The entity requires a page named Non-conformity and a subpage named Non-conformity Lines to store the information.
When a purchase order with incorrect quantity or quality issues is received, the entity must create a non-conformity document in the system. The following information must be included in the document:
o Non-conformity Number: must use the No. Series table from Business Central online to manage this field and use these features:
o Alphanumeric values
o Number format that includes "NC" and the year as part of the number; for example, NC24-001
- Non-conformity Date: stores only the creation date
- Vendor No.: stores the number of the vendor that sent the items; only vendors from the company must be included
- Owner: code of an employee defined in the company
- Receipt No.: must meet the following conditions:
o Be an existing receipt No.
o Be received from the vendor indicated in the Vendor No. field
- Comments: can include comments with rich text and pictures to illustrate quality problems
- Status: includes non-conformity statuses, such as:
o Open
o Notified
o Closed
- Lines must contain the following details:
o Item No.: item received (for existing inventory items only)
o Description: item description
o Quantity: non-conforming quantity
- Non-conformity Type:
o Quality
o Quantity
o Delivery date
The serial numbers of the non-conformities and the period in which they can be created must be in a configuration table and its corresponding page to allow them to be modified for the users.
You need to define the data types for the fields of the Non-conformity table.
Which two data types should you use? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
Answer: A,E
Explanation:
If you are using the standard No. Series you need to use a Code[20] on the field.
NEW QUESTION # 12
You need to handle the removal of the Description field and the Clone procedure without breaking other extensions.
Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.
NOTE: More than one order of answer choices is correct. You will receive credit for any of the correct orders you select.
Answer:
Explanation:
Explanation:
In Business Central, when you need to handle the removal of fields and procedures to ensure that other extensions are not affected by these changes, you typically follow a two-step deprecation process. This allows other developers and users to adapt to the changes before they are fully enforced. Here are the steps to handle the removal:
* Mark as Obsolete: In the first version where the decision to remove the field or procedure is made, you set the ObsoleteState to Pending and provide an ObsoleteReason. This doesn't remove the feature but indicates to users and developers that it will be removed in the future. This step is crucial for backward compatibility.
* Removal: In a subsequent version, after users have had time to adapt to the deprecation warning, you can then remove the field or procedure or set the ObsoleteState to Removed.
Based on these guidelines, here are the three actions you should perform in sequence:
* Set the Description field as ObsoleteState = Pending and ObsoleteReason = 'Not in use' in version
2.0.0.0.
* Set the Clone procedure as ObsoleteState = Pending and ObsoleteReason = 'Not in use' in version
2.0.0.0.
* Remove the Description field from the Issue table in version 2.0.0.1.
These steps will ensure that anyone using the Description field or Clone procedure will receive a warning about the pending deprecation before it is actually removed, thereby minimizing the impact on other extensions and providing a clear path for migration.
When handling the removal of fields and procedures in Microsoft Dynamics 365 Business Central, the process should be carried out in a way that allows other extensions or dependent features to adapt to the changes without causing immediate failures.
* Set Obsolete State and Reason for Description Field (Version 2.0.0.0): The first step involves marking the Description field as obsolete by setting the ObsoleteState to 'Pending'. This is a non-breaking change, signaling to other developers and users that the field is planned for removal in a future version.
An ObsoleteReason should also be provided to explain why the field is being deprecated.
* Set Obsolete State and Reason for Clone Procedure (Version 2.0.0.0): Similarly, the Clone procedure should be marked as obsolete with the ObsoleteState set to 'Pending'. This indicates that the procedure is no longer in use and will be removed in the future. Providing an ObsoleteReason is best practice as it explains the rationale behind the decision.
* Remove the Description Field (Version 2.0.0.1): In the subsequent version, after the developers and users have been given time to adapt to the deprecation notice, the Description field can be safely removed from the Issue table. This is considered a breaking change, hence it is done after the field has been marked as obsolete in a previous version.
The reason for not removing the Description field and Clone procedure immediately in version 2.0.0.0 is to avoid causing runtime errors for any extensions or integrations that may depend on these components. By following this sequence, you provide a clear deprecation path that helps maintain the stability of the overall system while evolving the schema.
Topic 2, Case Study Alpine Ski House
Alpine Ski House is a company that owns and operates hotels, restaurants, and stores. Currently, the company uses the following software and interlace:
* Property management software (PMS) to manage hotel rooms
* On-premises accounting software to generate sales invoices and create purchase orders
* An API that allows restaurants and stores to obtain necessary information Restaurants and stores use standalone software for point of sale (POS) devices. Each day, the POS terminals generate a text file of sales data and save the files in a serval folder. An account assistant must manually import the files to the current software tables to be processed by the system.
The general manager receives several reports monthly from department managers. The reports take too much time to prepare.
The company is moving from a different system to Business Central online to manage the whole company.
The company plans to increase efficiency in every department by using APIs to obtain or share information between the different systems.
Each department involved in purchasing must be able to make purchase requests automatically and easily.
The departments do not need access to the full ERP management system.
Alpine Ski House requires the development of several extensions for the planned improvements. Business Central design patterns must be used to develop all extensions.
Alpine Ski House must develop the following pages:
* Pages that provide multiple configurations in a multistep dialog, like a wizard, to provide required information when the extensions are first installed
* Department-specific Role Center pages to show relevant information and pages with additional information The IT department plans to use Power 61 to analyze departmental information. The database must be configured to provide optimal performance.
The housekeeping department requires the following to increase efficiency and help avoid data entry errors:
* A Housekeeping Role Center to minimize navigation to relevant areas In Business Central online and to show relevant information in it
* Pages to embed into a new Room page to show additional information about the Room entity
* A table named Room Incident for the housekeeping team to enter room issue information
* A Housekeeping canvas app that connects to an extension
The department requires the development of an extension with a new API page named RoomsAPI.
* The housekeeping team will use RoomsAPI to publish room details, update when work is complete, or provide repair notifications from the canvas app.
* This custom API page must expose a custom table named Rooms and have an ID 50000. The table must be able to update from the PMS. The PMS team must know the end to connect to the custom API.
* A developer provides the following details for the API page:
APIPublisher = 'alpine';
APIGroup - 'integration';
APIVersion - 'v2.6';
fntityName # 'room';
EntitySetName = 'rooms';
* The extension must be published in Business Central online and include a list page named Room List that includes all hotel rooms.
* Installation or updates to this extension must meet the following requirements:
o Some web services must be published automatically.
o The version of the specified application's metadata must be obtained in AL language.
o The code required to perform tasks cannot be accessible from other parts of the application.
The Room Incident table information must include the following fields:
* Incident entry: An incremental number
* Room No.: A room from the Room table
* Incident Date: The work date
o The table definition in the Room Incident table must autofill the Incident Date when the housekeeping team inserts a new record, o The value for Incident Date must be the work date configured in the Business Central online client.
* Status: Includes the following options lo identify the status of the incident:
o Open: When the Room Incident is created
o In Progress: When someone starts repair work
o Closed: When the incident is solved
* Incident Closing Date: Auto-updating field (when the status passes to Closed, the field will update with the work date)
* Incident Description: Text
* Image. Media data type
o The stored picture must be downloadable from a menu action.
o A Room Incident page must be developed to contain the download action.
To increase efficiency, the new system must manage the generated data from the restaurants and stores directly by using the API on the POS terminals.
* The company requires a code unit called from a job queue to read the information from the POS terminal APIs.
* The POS terminal information must be stored in a table named POS Information, have an ID 50100. and be editable on a page.
* The account manager requires an option on the menu of the page to run the process manually.
To analyze the information received from the POS terminals, the company requires:
* A custom API named ticketAPI to export the information to Power BI
* Use of the Read Scale-Out feature to improve database performance
The purchasing department requites a new entity in Business Central online to log non-conformities of goods received from vendors. The entity must be set up as follows:
* The non-conformity entity must have two tables:
o a header with common information
o one or more lines with the detailed received items that are non-conforming
* The entity requires a page named Non-conformity and a subpage named Non-Conformity Lines to store the information.
When a purchase order with incorrect quantity 01 quality issues is received, the entity must create a non- conformity document in the system. The following information must be nick the document:
* Non-conformity Number: must use the No. Series table from Business Central online to manage this field and use these features:
o Alphanumeric values
o Number format that includes "NO and the year as part of the number: for example, NC24-001
* Non-conformity Date: stores only the creation date
* Vendor No.: stores the number of the vendor that sent the items; only vendors from the company must be included
* Owner: code of an employee defined in the company
* Receipt No.: must meet the following conditions:
o Be an existing receipt No.
o Be received from the vendor indicated in the Vendor No. field
* Comments: can include comments with rich text and pictures to illustrate quality problems
* Status: includes nonconformity statuses, such as:
o Open
o Notified
o Closed
* Lines must contain the following details:
o Item No.: item received (for existing inventory items only)
o Description: item description
0 Quantity: non-conforming quantity
0 Non-conformity Type:
# Quality
# Quantity
# Delivery date
The serial numbers of the non-conformities and the period in which they can be created must be in a configuration table and its corresponding page to allow them to be modified for the users.
NEW QUESTION # 13
You develop a table named Contoso Setup and a page.
You plan to use No. Series to automatically assign a unique number to data entries. You set up No. Series on the Vendor Nos. field of the Contoso Setup table.
You need to apply the No. Series Design Pattern to the trigger Onlnsert().
Which four code segments should you use to develop the solution? To answer, move the appropriate code segments from the list of code segments to the answer area and arrange them in the correct order.
Answer:
Explanation:
Explanation:
Here is the correct sequence of the four code segments:
* if " No. " = ' ' then begin
* ContosoSetup.Get();
* ContosoSetup.TestField( " Vendor Nos. " );
* NoSeriesManagement.InitSeries(ContosoSetup. " Vendor Nos. " , xRec. " No. Series " , 0D, " No. " , " No. Series " ); end;
* Check for empty value: The standard pattern for OnInsert is to only assign a number automatically if the user has not manually entered one. Therefore, you start with if " No. " = ' ' then begin.
* Retrieve Setup: You must retrieve the setup record to access the configured No. Series code. The singleton pattern for setup tables uses ContosoSetup.Get();.
* Verify Configuration: Before attempting to use the series code, best practice dictates you ensure it is actually populated in the setup table. ContosoSetup.TestField( " Vendor Nos. " ); checks this field.
* Initialize Series: Finally, you call the InitSeries function.
* Argument 1 (Source): ContosoSetup. " Vendor Nos. " is the field containing the Series Code (as stated in the prompt).
* Argument 2 (Previous): xRec. " No. Series " handles standard renaming/validation logic.
* Argument 4 & 5 (Targets): " No. " and " No. Series " are the fields on the current record being updated.
* Note: The other available InitSeries block is incorrect because it tries to read a field named " No.
Series " from the ContosoSetup table, which does not match the prompt ' s description.
NEW QUESTION # 14
You need to configure the Subcontract Docs extension to translate the fields.
Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.
Answer:
Explanation:
Explanation:
NEW QUESTION # 15
......
The CramPDF is a leading platform that is committed to making the MB-820 exam dumps preparation simple, quick, and successful. To achieve this objective CramPDF is offering real, valid, and updated Microsoft MB-820 practice questions in three different formats. These formats are CramPDF Microsoft MB-820 PDF Dumps Files, desktop practice test software, and web-based practice test software. All these CramPDF Microsoft Dynamics 365 Business Central Developer exam questions formats are easy to use and compatible with all web browsers, operating systems, and devices.
Valid MB-820 Test Simulator: https://www.crampdf.com/MB-820-exam-prep-dumps.html
DOWNLOAD the newest CramPDF MB-820 PDF dumps from Cloud Storage for free: https://drive.google.com/open?id=1GxErHWOS3b_wYVKJdTPG4Dkg00wxRjTJ