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.
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.
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?
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.
You have a decimal variable named AmountlCY.
You need to round up the variable to four decimal places.
Which result value should you use?
To round up a decimal variable to four decimal places in Microsoft Dynamics 365 Business Central, you should use the Round function with specific parameters. The correct formula is Result := Round(AmountLCY, 0.0001, '=') (B). This function rounds the AmountLCY variable to the nearest value based on the second parameter, which is 0.0001 in this case, representing four decimal places. The third parameter, '=', specifies that the function should round to the nearest value, which effectively rounds up the value when it's halfway between two possible rounded values. This approach ensures that the AmountLCY variable is accurately rounded to four decimal places, which is essential for financial calculations and reporting to maintain precision.
You need to access the RoomsAPI API from the canvas app.
What should you do?
API Publishing for Extensions:
In Business Central, when creating custom APIs like RoomsAPI, it is important to ensure that they are automatically published during the installation or upgrade of the extension.
To achieve this, you can include a codeunit of type Install in the extension that explicitly publishes the custom API (RoomsAPI) as a web service. This ensures that it is available for use immediately after the extension is deployed without requiring manual intervention.
Codeunit Type:
A codeunit of type Install runs when the extension is installed or upgraded. This type of codeunit can be used to perform setup tasks such as publishing web services or APIs like RoomsAPI.
Why Not Other Options?
Option A (default API configuration): This would not automatically publish the RoomsAPI. Default APIs do not cover custom APIs.
Option B (enable APIs for the environment): Enabling APIs in Business Central allows the standard APIs to be used, but custom APIs still need to be manually published.
Option C (publish via Web Services page): This would work but requires manual intervention to publish RoomsAPI, which does not fulfill the requirement of automatic publishing during installation.
Reference Documentation:
Codeunit Types in Business Central
You are developing an app that will be published to Microsoft AppSource.
The app requires code analyzers to enforce some rules. You plan to add the analyzers to the settings.json file.
You need to activate the analyzers for the project.
Which three code analyzers should you activate to develop the app for AppSource? Each correct answer presents part of the solution
NOTE: Each correct selection is worth one point.
When developing an app for Microsoft AppSource, it is crucial to adhere to specific guidelines and standards to ensure compatibility and compliance. The three code analyzers you should activate are:
CodeCop (A): This is the default analyzer for AL language extensions. It enforces the AL Coding Guidelines, ensuring that the code follows best practices for readability, maintainability, and performance. It checks for a wide range of issues, from syntax errors to best practice violations, making it essential for any AL development.
PerTenantExtensionCop (D): This analyzer is specifically designed for extensions that are intended to be installed for individual tenants. It includes rules that ensure the extension does not interfere with the per-tenant customizations and adheres to the guidelines for extensions that can be safely installed and uninstalled without affecting the underlying application.
AppSourceCop (E): This analyzer is tailored for extensions that are intended for publication on Microsoft AppSource. It enforces additional rules that are specific to AppSource submissions, such as checking for the use of reserved object ranges and ensuring that all prerequisite dependencies are correctly declared. This is crucial for ensuring that your app meets all the requirements for listing on AppSource.
By activating these three analyzers, developers can ensure their app adheres to the standards required for AppSource, as well as maintain high code quality and compatibility with Business Central.
