Finance | Project Operations, Human Resources, ...

System Admin Cannot View "Number Sequence Code" Column on Parameter Forms.

(4) Share

Report

Posted on by okanpiskin

Hi Everyone,

I am facing a very unusual and specific issue regarding the visibility of the "Number Sequence Code" field in Dynamics 365 Finance & Operations, and I wanted to share it with the community to see if anyone else has encountered this or has a solution.

The Issue:
Even though I have the System Administrator role, I cannot see the "Number Sequence Code" column in any parameter screen (taking Accounts payable parameters as an example here), despite using the Standard View.

When I try to manually add the column using the "Insert column" feature, the field appears, but it is completely empty and locked for editing (read-only).

In fact, even the reference row for an already assigned number sequence (such as OTS-INCM, which should be mapped to One-time supplier) appears completely blank in the grid.

For reference, this is how it normally looks for another System Admin user on their machine.

Troubleshooting Steps Taken So Far:

I cleared my user's Usage Data in D365 and completely cleared my browser's cookies/cache.
I tried logging in via a different browser on my PC and repeated the first step.
I granted the System Admin role to a different test user account on my local PC, but the issue persisted for that user on my machine as well.
I checked with another System Admin on their own physical PC, and they could see and edit the field perfectly fine using the Standard View.
Interestingly, when I logged into a different PC (a DEV environment VM in Azure) using my own problematic user account via Edge browser, I was able to see and edit the field normally.

It seems to be a highly specific local machine, display, or browser-rendering related issue rather than a security or D365 personalization setup problem. I haven't encountered an error like this caused strictly by the local PC environment in years.

Has anyone faced something similar? What could be causing this specific local rendering/behavior fault for standard grid columns?

Wishing everyone happy, error-free AX and D365 days!

Best regards,
Okan

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (10)

Answers (0)

Sort by

Subra 1,320 on at

Like (1)

Report
Copy link

Link copied!

Hi @okanpiskin

Do you have any other roles has been assigned to particular user other than system adminstrator? if yes, there might be some conflict with user roles.

Which environment you have this issue and please specify which version you are using?

Thanks,
Subra

Was this reply helpful? Yes No
okanpiskin 33 on at

Like (0)

Report
Copy link

Link copied!

Hi Subra,
Thank you for your response and for looking into this.

To answer your questions:
Regarding User Roles: No, the user only has the System Administrator role assigned, so there shouldn't be any security privilege conflicts. Furthermore, when I assigned the System Admin role to a completely different test user account and logged in on this same local PC, that user experienced the exact same issue. Conversely, when I used my own problematic user account on a completely different PC (Azure DEV environment), the column appeared and worked perfectly fine. This strongly indicates the issue is tied to the local machine/environment rather than the user profile or security roles.
Environment & Version: This issue is occurring in our Production environment. The platform/application version we are currently running is 10.0.47 (10.0.2527.109).

Since it only breaks on this specific client machine regardless of the user account, and works fine for the same user on other machines, it feels like a very bizarre local cache, display scaling, or hardware acceleration rendering glitch in the browser that somehow targets just this grid column.
Any insights based on this behavior?

Was this reply helpful? Yes No
Subra 1,320 on at

Like (0)

Report
Copy link

Link copied!

Hi

It's looks like strange issue and we are not able replicate the issue in other user or different environments.

I hope you have tried with different browser and please download the latest version as well.

Thanks,
Subra

Was this reply helpful? Yes No
Suggested answer

Giorgio Bonacorsi 3,465 on at

Like (2)

Report
Copy link

Link copied!

Hello,

Are you using the out-of-the-box system admin role?

Usually the company create a duplicate or a new system admin role personalize for them.

If it's personalize try to check if you have these 2 privileges:

Thank you, keep us in touch with the evolution of your issue.

Thank you,

Giorgio

Was this reply helpful? Yes No
okanpiskin 33 on at

Like (0)

Report
Copy link

Link copied!

Hi Giorgio,

To clarify, I am using the standard System Administrator role. No duplicates or personalized admin roles have been created or assigned.
As you mentioned, if it were a security or privilege issue, it should have followed my user account across different devices. However, since the exact same standard role works flawlessly when I log in from another PC (and works perfectly for other admins on their own machines), we can confidently rule out security setups or missing privileges.

We are certain that the root cause is strictly isolated to this specific local PC's environment. It seems to be a very rare browser-rendering, local cache, or hardware-related glitch that specifically targets this grid element. We are currently trying to pinpoint exactly what local variable (like display scaling, hardware acceleration, or registry-level browser glitches) is triggering this behavior.

I will definitely keep the thread updated as we dig deeper into the source of this machine-specific issue.
Thanks again for your support,

Was this reply helpful? Yes No
Waed Ayyad 9,183 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hi,

Do you have more than legal entities? Did you try to change legal entity?

Are you working on D365 Cloud or on-Premises?
Do you have any data security on production?

Did you try to open another module and check number sequence there?

Was this reply helpful? Yes No
André Arnaud de Cal... 305,815 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hi Okan,

I haven't seen this issue before. You mentioned that this is happening on all parameter forms where you can configure number sequences. Is this a development environment where an extension exists that by accident hides this field?

What happens if you assign another role where the user can enable a module? Is your user then able to see the field?

When another user checked it on their PC, was that the same environment or another one?

Was this reply helpful? Yes No
okanpiskin 33 on at

Like (1)

Report
Copy link

Link copied!

Hi Waed,

Thank you for your response.

Legal Entities: Yes, we have multiple legal entities. I tried switching between different entities, but unfortunately, the behavior remains exactly the same—the "Number sequence code" column stays missing or blank/locked across all of them on this specific PC.

Cloud vs. On-Premises: We are running on D365 Cloud (Finance & Operations).

Data Security (X++ / Extensible Data Security): We do not have any custom Extensible Data Security (XDS) or specific data security policies applied to this role or environment that would restrict this grid. If it were a security or XDS policy issue, it would also affect my user account when I log in from other machines, but it works perfectly fine on other PCs.

Other Modules: Yes, I checked the Number Sequences tab in other module parameters (such as Accounts receivable parameters and General ledger parameters). The issue is global across the entire environment on this machine; the column is missing or blank everywhere.

Since all of these application-level checks (entities, modules, security) work flawlessly as soon as I switch to a different physical computer using the exact same user account, it completely points back to a bizarre local machine or browser-rendering anomaly rather than a D365 configuration issue.

Thank you.

Was this reply helpful? Yes No
okanpiskin 33 on at

Like (0)

Report
Copy link

Link copied!

Hi Mr. André,

To answer your questions and share the exact scope of our environment:

Development Extensions / Environment: This issue is occurring in our Production environment, not a development one. Since it is Production, the codebase is identical for everyone. If an extension or custom code was accidentally hiding or modifying this field, it would affect all users across all machines. However, it only happens on this specific physical PC.

Assigning Another Role: I haven't tried assigning a non-admin module-specific role to this user on this PC yet. However, when I assigned the standard System Administrator role to a completely different test user account on this exact same PC, that user experienced the same issue. Conversely, when I logged into a DEV environment VM on Azure using my own problematic user account via Edge, the field appeared and worked normally. This confirms that the application behaves correctly when the client machine changes.

Same vs. Other Environments for Other Users: When another user checked it on their PC, it was the exact same Production environment. They can view, select, and edit the number sequence codes without any issues using the same Standard View.

Everything we test keeps pointing away from D365 configurations, security, or customizations, and points directly to a local client-side anomaly—likely a deep browser caching issue, a local Windows display scaling artifact, or a hardware acceleration rendering glitch that specifically fails to render this particular grid control.

Thank you.

Was this reply helpful? Yes No
Suggested answer

okanpiskin 33 on at

Like (2)

Report
Copy link

Link copied!

Hi everyone,

Quick Update: I just restarted the problematic local PC, logged back into the same Production environment with the exact same user account/privileges, and I can confirm that the issue is now completely resolved! The "Number Sequence Code" column is back, visible, and fully editable in the Standard View.

Given all the iterations and isolation steps we went through, I strongly suspected it would come down to a local OS/client-level reset.

However, the main reason I wanted to share this bizarre case here is that I am still genuinely curious about the root cause of this artifact. If there is anyone in the community who has experienced this exact visual glitch before and knows the deep technical reason behind it (e.g., a specific Chromium rendering deadlock, local Windows display/graphics cache corruption, or hardware acceleration fault targeting specific grid controls), I would love to hear your valuable insights!

Otherwise, for anyone who runs into this frustrating anomaly in the future, the quick and definitive solution is simply to restart your physical machine.

Thank you all so much for your support, time.

Wishing everyone happy, error-free AX and D365 days!

Was this reply helpful? Yes No