[Rockwith nav]

Up

0

Down

::

This is a rare case, but the only possibility I can think of right now is this, since you are able to post some transactions, you need to identify which ones work and which ones don’t. There may be a pattern, and it’s possible that for certain scenarios, the system is not allowing you to transact for some reason. It could be transaction-specific, with a certain security blocking the process.

[Lori Dostie]

Up

0

Down

::

Check your user license type. Limited licenses can not post some transactions and it presents as a permission error.

[andrew alwin]

Up

0

Down

::

We’ve seen similar “random permission” behavior in NAV → Business Central upgrades. In most cases, it’s not truly random. It’s usually permission evaluation + caching + object mismatch happening together.

A few things I’d specifically check:

Permission Set type (User vs System vs Extension)

If you’re still using legacy NAV-style permissions or partially migrated sets, BC can behave inconsistently. Try moving users fully to AL-based permission sets.

Indirect permissions missing

Posting often fails not on the main table but on related tables (ledger, dimensions, temp buffers). Admins bypass this, users don’t. That’s why it “works sometimes”.

Security cache issues

Restarting NST helps, but also try:

Force user re-login

Clear session via admin center / PowerShell

BC can cache permissions per session, causing inconsistent behavior.

Customization / extensions conflict

If any posting logic is extended, check if custom code is accessing tables without proper permissions. This is very common after upgrades.

License + permission mismatch

Sometimes users assigned lower-tier licenses hit permission issues during posting scenarios that worked in NAV.

Telemetry clue you mentioned

If telemetry shows inconsistent evaluation, I’d strongly suspect multiple permission sources overlapping (custom + standard + extension).

One quick test:

Create a clean test user with only standard BC permission sets, no customizations. If posting works 100%, the issue is definitely in your custom/security layer.

[Jim Donahue]

Up

0

Down

::

Hi Mark,

The Dynamics Communities team wanted to reach out and ask that no longer post links to partner websites as the forums are not a place to advertise and is against community policy.

You can continue to ask questions that you have regarding Dynamics products as this is helpful to the community, but any more posts with links to a product or service will be marked as spam and removed.

[Meenakshi Singh]

Up

0

Down

::

This could also be because of a permission mismatch between your EntraID login and BC login permissions. If it’s allowing you to post sometimes and not others. Indirect posting permission sets in BC would allow for that, too.