Microsoft Dynamics 365 | Integration, Dataverse...

Button is not visible in Higher env

(2) Share

Report

Posted on by Rahul Mamgain

Hi All,

I have two buttons on my entity form: Delete and Deactivate.

My requirement is:

1: Hide the Delete button (it was originally visible)

2: Unhide the Deactivate button (it was originally hidden)

I created a solution, added the entity with metadata, updated the ribbon to hide the Delete button and show the Deactivate button. In my development environment everything worked as expected.

However, after importing the solution into the higher environment, the Delete button was correctly hidden, but the Deactivate button is still not visible.

Can you please suggest why this might be happening or what I should check?

Categories:

Dynamics 365 general

I have the same question (0)

All responses (7)

Answers (0)

André Arnaud de Cal... 303,085 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi,

Can you tell us what Dynamics 365 application this question is related to? There are several different solutions in the Dynamics 365 family, like Sales, Finance, Supply Chain Management, Project Operations, and Customer Insights. Or are you building a model-driven app?

Was this reply helpful? Yes No
Rahul Mamgain 12 on at

Like (0)

Report
Copy link

Link copied!

@André Arnaud de Calavon i am building model driven app. and when i download xml file of solution it only include delete button as hidden not deactivate. on the top of that i have checked any JS which could cause the button hidden but everything look fine.

Was this reply helpful? Yes No
Rahul Mamgain 12 on at

Like (1)

Report
Copy link

Link copied!

Could this be happening because the entity was previously moved using a different solution, and that older solution still holds the ribbon definition. As a result, it could be overriding the changes I made in the new solution ?

Was this reply helpful? Yes No
Suggested answer

Anthony Blake 3,061 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

@Rahul Mamgain I believe you could be correct here.

If you have deployed changes in 2 solutions you may have this kind of stack:

Solution 2

Solution 1

Base layer

When you the update your buttons in Solution 1 and redeploy, because this replaces solution 1, solution 2 is still higher so may be over-layering your change.

Can you make the change in "Solution 2" (top layer) to test?

Was this reply helpful? Yes No
Rahul Mamgain 12 on at

Like (0)

Report
Copy link

Link copied!

@Anthony Blake could this happen because on my higher env. there is unmanaged layer is top layer on button?

Was this reply helpful? Yes No
Anthony Blake 3,061 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

@Rahul Mamgain yeah I think so, it could be managed or unmanaged, but creating that top layer is why you need to be careful not to create unmanaged layers, as they can behave just like this. Check the layers, what do you see?

Was this reply helpful? Yes No
Suggested answer

Rahul Mmgin 2 on at

Like (0)

Report
Copy link

Link copied!
Hi everyone,

Thank you for taking the time to review my issue and for your valuable suggestions.

I was able to resolve the problem, and it turned out not to be a technical limitation but rather a solution deployment and layering issue.

What I observed and how it was resolved:

Initially, I reverted all ribbon customizations in the lower (development) environment and exported the solution to the QA environment to ensure a clean baseline.

After that, I re-applied the required changes (hiding the Delete button and unhiding the Deactivate button).

This resolved the issue on the entity form, but the Deactivate button was still hidden on the grid.

To fully resolve this, I moved the solution from a higher environment (UAT) back to Development, made the necessary ribbon updates there, and then redeployed the solution to QA.

After following this clean promotion path, both buttons behaved correctly on the form and the grid.

1 people found this reply helpful.

Was this reply helpful? Yes No