A company uses Business Central.
The company has sales orders that have a different location in the header than in the customer's card. You plan to add a check on sales order posting.
The check must meet the following requirements.
* Sales Order must have the same Location Code as the Location Code set up on the customer's card.
* Must not be run in preview mode.
* Must be run even if the user is only shipping items and not invoicing.
You create an event subscription for codeunit 80 "Sales-Post" You need to identify which event to subscribe to Which event should you identify?
A.
B.
C.
D.
This event occurs before posting a sales document.
PreviewMode is available in the parameters, which allows checking whether the process is being run in preview mode.
This event is typically used for sales order posting and can be used for both shipping and invoicing.
This event matches the requirements because:
You can check if PreviewMode is false.
It can run for both shipping and invoicing.
A company uses Business Central Users in DepartmentA are assigned a base application permission set.
The company observes that Departments can display a critical page that should be unavailable to the department.
You need to resolve the system control issue.
What should you do?
Permission sets control access to objects (such as pages, tables, reports) in Business Central. By creating a new permission set that specifically excludes the critical table (or page) and assigning this permission set to the users in Department A, you can prevent them from accessing the page.
Option A (creating a different role center page) is incorrect because role centers control the user interface, but do not directly restrict access to specific pages or tables.
Option B and Option C (extending the base application permission set) are not the best options because extending permission sets typically involves adding permissions, not removing access. The question requires restricting access to a critical page, so simply including or excluding permission sets won't solve the issue at the table or page level.
Option D (creating an entitlement object) is not relevant here, as entitlements are used in more complex licensing scenarios or environments.
Summary:
Creating a permission set object that specifically excludes access to the critical table or page and assigning it to the users will solve the problem effectively.
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.
You need to add a property to the Description and Comments fields with corresponding values for the control department manager.
Which property should you add?
You need to determine why the extension does not appear in the tenant.
What are two possible reasons for the disappearance? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.
In the context of Microsoft Dynamics 365 Business Central, an extension may not appear in the tenant for several reasons, particularly after an upgrade to a new major version.
Option A suggests that the extension was published as a DEV extension, which typically would not cause it to disappear after an upgrade because DEV extensions are intended for development and testing within sandbox environments.
Option B indicates that the extension was not compatible with the new version within 60 days of the first notification. This is a likely reason because Microsoft enforces compatibility rules, and extensions that are not made compatible within the specified timeframe might be removed or disabled.
Option C refers to the extension being published as a PTE (Per-Tenant Extension) and mentions the Platform parameter not being updated. This could cause issues, but not specifically the disappearance of the extension after an upgrade.
Option D expands on Option C by adding that both the Platform and Runtime parameters were not updated in the application file. This is a critical aspect because if these parameters are not correctly set to indicate compatibility with the new version of Business Central, the extension could be disabled or removed.
Option E is similar to Option B but mentions a 90-day period. This option does not align with standard Business Central practices for version compatibility requirements.
Marg
2 months agoRodolfo
3 months agoAnnelle
4 months agoGayla
5 months agoRosita
6 months agoLacey
7 months agoHan
7 months agoCarry
8 months agoShenika
8 months agoClaudia
8 months agoLavonne
9 months agoDaren
9 months agoLashawnda
9 months agoStaci
10 months agoJacquelyne
10 months agoMinna
10 months agoJohnetta
11 months agoKenneth
11 months agoDell
11 months agoAaron
11 months agoKimbery
11 months agoGlenn
12 months agoPaz
1 years agoTashia
1 years agoJenelle
1 years agoCory
1 years agoJade
1 years agoStephaine
1 years agoRuthann
1 years agoCortney
1 years agoMurray
1 years agoElvera
1 years agoLawrence
1 years ago