You must simulate the user interaction of selecting a posting option. The options must include:
* Ship
* Invoice
* Ship & Invoice
You need to create a test codeunit to run the test.
What should you use?
Answer : B
Handler methods are used in tests to simulate user interactions, such as responding to dialogs, confirmation messages, or option selections. Since you need to simulate the user interaction of selecting a posting option (Ship, Invoice, Ship & Invoice), a Handler method would be the appropriate choice for capturing this kind of user input.
Normal attribute and Test attribute are used for marking methods for test execution, but they do not simulate user interaction, making Handler method the correct answer.
For more details, see the Microsoft Docs on Test Codeunits and Handler Methods.
You are customizing Business Central by using Visual Studio Code. You create a project that will extend Business Central. The AL extension contains JSON files, which are automatically generated and are used to store configuration data
For testing purposes, you plan to add the following changes to the files:
* Specify that page 21 must be opened after publishing.
* Enable debugging
* Disable the capability to download the source code
You need to add the configurations to the JSON files.
Which two configurations should you add? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.
Answer : C, E
You are customizing Business Central using Visual Studio Code and JSON files for configuration.
You plan to:
Open page 21 after publishing.
Enable debugging.
Disable the capability to download the source code.
Which configurations should you add?
The options involve two primary JSON files: launch.json and app.json, and configuration tags like startupObjectId and resourceExposurePolicy.
A company plans to change a field on the Resource Card page in a Base Application.
You need to hide the field "Unit Price" from the Resource Card page.
Which code snippet should you use?
A.
B.
C.
D.
Answer : D
To hide the field 'Unit Price' from the Resource Card page in Microsoft Dynamics 365 Business Central, you need to modify the visibility property of the field using the modify keyword, which allows you to change the properties of an existing field on a page.
Explanation=
modify('Unit Price') is the correct way to target an existing field on a page (like the Resource Card page).
The line Visible = false; makes the field invisible on the page.
Here's a breakdown of why each option is right or wrong:
Option A:
Uses addlast('Unit Price'), which is incorrect because you are not adding a new field; you're modifying an existing one. Also, Visible = false is correct for hiding a field, but the wrong method (addlast) is used.
Option B:
Uses modify('Unit Price') with Enabled = false;. This would disable the field (make it non-editable), not hide it. The field would still be visible, so this does not meet the requirement.
Option C:
Uses addlast('Unit Price'), which is incorrect, and Enabled = false;, which would disable the field, not hide it.
Option D:
modify('Unit Price') { Visible = false; } is the correct syntax for hiding the field on the page.
Correct Code Snippet:
modify('Unit Price')
{
Visible = false;
}
This hides the 'Unit Price' field from the Resource Card page.
You have an XMLport that exports items from a database to an XML file.
You need to change the export format from XML to CSV.
What should you do?
Answer : E
XMLport Overview In Microsoft Dynamics 365 Business Central, XMLports are used for importing and exporting data in XML, CSV, or other text formats. By default, XMLports are designed to work with XML data, but they can also handle delimited text formats like CSV (Comma-Separated Values).
Requirement Clarification The requirement is to change the export format from XML to CSV. CSV is a text-based format, not an XML format. To accommodate this, you need to change how the XMLport handles data during export.
Properties of XMLport
The Format property in XMLports controls whether the output format is XML or a text-based format such as CSV.
The VariableText option of the Format property specifies that the data should be exported in a variable text format, like CSV.
The XMLports default to an XML format, but by setting the Format property to VariableText, you can change the export to CSV format or another text-delimited format.
Explanation of Correct Answer (E) To switch from XML to CSV export:
You need to change the Format property of the XMLport to VariableText.
The VariableText option allows for the export of data in a non-XML format, which is precisely what CSV represents (a comma-delimited text file).
Why Other Options Are Incorrect
Option A (Change the Direction property to Both): The Direction property controls whether the XMLport is used for Import, Export, or Both (import and export), but it does not affect the file format (XML vs. CSV). Hence, this is irrelevant to the file format change.
Option B (Change the FormatEvaluate property to Legacy): The FormatEvaluate property is not related to changing the export format. It deals with the evaluation of the data format during the processing but doesn't change the format type (XML or CSV).
Option C (Change the XmlVeisionNo property to 1.1): The XmlVersionNo property defines the XML version used for the export (such as 1.0 or 1.1). This only applies to XML exports and does not change the format to CSV.
Option D (Fill the FileName property with Items.csv): While this option would specify the name of the file being exported (i.e., 'Items.csv'), it doesn't control the format of the export itself. The actual format change is controlled by the Format property.
Developer Reference from Microsoft Documentation According to the official Microsoft documentation for XMLports in Business Central, the Format property is critical for determining how data is structured for export. To change the file format from XML to CSV, developers need to set the Format property to VariableText. This allows for export in a text-delimited format, which is ideal for CSV.
XMLport Properties - Format Property
How to: Export Data in Text Format Using XMLports
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear on the review screen.
A company creates a Business Central app and a table named MyTable to store records when sales orders are posted.
Users report the following issues:
* The users receive permission errors related to MyTable.
* Users are no longer able to post sales orders since installing the new app.
* The users cannot access the list page created in MyTable.
You need to resolve the user issues without creating new permission sets. You must use the principle of least privilege.
Solution: Assign a SUPER permission set.
Does the solution meet the goal?
Answer : B
Assigning a SUPER permission set to all users would indeed resolve the permission errors and access issues reported by the users, as it grants full permissions across all objects and data in Business Central. However, this approach contradicts the principle of least privilege, which advocates for providing only the minimum levels of access necessary for users to perform their jobs. The SUPER permission set would excessively elevate user privileges, potentially leading to security risks and unintended modifications to critical data. Therefore, while assigning the SUPER permission set might technically resolve the immediate issues, it does not meet the goal of adhering to the principle of least privilege and is not a recommended solution.
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear on the review screen.
A company creates a Business Central app and a table named MyTable to store records when sales orders are posted.
Users report the following issues:
* The users receive permission errors related lo MyTable.
* Users are no longer able to post sales orders since installing the new app.
* The users cannot access the list page created in MyTable.
You need to resolve the user issues without creating new permission sets. You must use the principle of least privilege.
Solution: In the MyTable object add the property InherentPermissions = Rl. Does the solution meet the goal?
Answer : B
The property InherentPermissions is used to automatically grant permissions to the table object it is applied to, but setting it to Rl (which seems to be a typo and should likely be 'RL' for Read and Insert permissions) is not sufficient in this scenario. The issues reported by the users suggest that they need more than just read and insert permissions on MyTable. Since users are unable to post sales orders, they likely need Modify, Delete, or Execute permissions on certain tables or objects related to the sales order process. Additionally, the inability to access the list page created in MyTable could be due to lacking Read permissions on other related objects or pages. Therefore, merely setting InherentPermissions = RL on MyTable does not comprehensively address the users' permission issues, especially when considering the principle of least privilege. A more tailored approach to permissions, potentially involving adjustments to the app's code or configuration to ensure proper permissions are applied where necessary, would be needed.
You are creating an entitlement object in Business Central to enable transactability for AppSource apps.
You must map the entitlement object to a plan in Partner Center.
You need to select the value of the Type property to use in the entitlement object.
Which value should you use?
Answer : A
In Business Central, when creating an entitlement object to enable transactability for AppSource apps and mapping it to a plan in Partner Center, the Type property of the entitlement object should be set to PerUserServicePlan (A). The PerUserServicePlan type is used to define an entitlement that is based on a service plan, which is typically how transactability features are managed for apps distributed through AppSource. This type of entitlement allows for the mapping of specific features or capabilities of the app to a service plan in Partner Center, enabling granular control over what users are entitled to use based on their subscription. The other values, such as Implicit (B), Unlicensed (C), and Role (D), are used in different contexts and do not apply to the scenario of mapping an entitlement object to a plan for AppSource apps.