Free MB-800 Microsoft Updates

In Dynamics 365 Business Central, when multiple permission sets are assigned to a user, the system combines the permissions from all assigned sets.

Key rules for permissions:

If a permission is set to Yes in any permission set, the user is granted that permission.

If a permission is set to Blank in one permission set, it means " no explicit permission, " not a denial.

A No value would explicitly restrict the permission, but Blank does not override a Yes from another set.

In the provided case:

CustomerMgmt permission set grants Insert = Yes on Table 18 (Customer).

ReceivablesMgmt permission set has Insert = Blank on the same table.

Since Yes and Blank are combined, the effective permission is Yes → the user can create a new customer.

Why not A or B?

A. The permission set order will allow a user to create a new customer → Incorrect because order does not matter. Permissions are aggregated across sets.

B. The Blank option will allow a user to create a new customer → Incorrect because Blank means no explicit permission. It does not give access on its own.

C. The Yes option will allow a user to create a new customer → Correct because Yes overrides Blank and grants the permission.

Microsoft Learn References

Permissions and Permission Sets

How Business Central Combines Permissions

In Dynamics 365 Business Central, when using Approval User Setup with Approver Chain as the limit type:

Each approver has a defined Approval Limit (the maximum amount they can approve).

If a document exceeds the requester’s approval limit, the workflow escalates through the Approver Chain until a user with sufficient limit is found.

The workflow continues until the purchase order reaches an approver with authority greater than or equal to the document amount.

For this question:

User1 creates a purchase order for $1,100.

Since the order is above User1’s limit, it escalates to User2.

If User2’s limit is not sufficient to fully approve $1,100, it then escalates to User3, who has a higher approval limit.

The workflow only releases the purchase order once all required approvers (User2 and User3 in this case) approve it.

Therefore, the correct chain of events is:

User2 receives the approval request first.

After User2 approves, it is routed to User3.

Once both User2 and User3 approve, the purchase order is released.

Microsoft Learn References:

Set up approval users and approval chains

Use approval workflows in Business Central