Customer experience | Sales, Customer Insights,...

Best Practice to Customise Navigation in Solutions?

(1) Share

Report

Posted on by NicholasHE

I have been working on customized forms and views in an unmanaged solution in my Dynamics 365 Sales Dev environment, that will be imported as a manages solution in the Dynamics 365 Sales Production environment. which is what the Microsoft Learn documentation recommends as best practice.

I now need to customise the main Navigation menu, which would be done by adding the Sales Hub app to my solution, and editing the menu. Is this best practice? When I do this, my solution has both the Sales Hub model driven App, and a Sitemap listed in the object, should I remove the model driven app, and only keep the sitemap?

Any links to articles explaining suggestions for solution development would be appreciated. The approach to copy and customise the forms is very simple and easy to see how you can have a customised version for your business without preventing future improvements from Microsoft. I hope there is a similar approach for commonly modified objects like sitemaps/navigation.

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

Muhammad.Affan 4,624 Super User 2025 Season 2 on at

Like (5)

Report

Hi Nicholas,

This thread is similar to your issue:

https://community.dynamics.com/forums/thread/details/?threadid=dd57dbd4-0090-4fb6-b64c-d8e857a77444

Refer these links too:

https://learn.microsoft.com/en-us/power-platform/alm/how-managed-solutions-merged

https://learn.microsoft.com/en-us/power-platform/alm/update-solutions-alm

Thanks

Affan

Please verify my answer once the issue is solved.

Was this reply helpful? Yes No
Suggested answer

Ben356 13 on at

Like (1)

Report

Hello NicholasHE

I have attempted to answer all queries, answers in bold.

Query: I now need to customise the main Navigation menu, which would be done by adding the Sales Hub app to my solution, and editing the menu. Is this best practice?

No, if you only need to modify navigation in the context of tables, charts then only the sitemap needs to be edited not the app.

Query: When I do this, my solution has both the Sales Hub model driven App, and a Sitemap listed in the object, should I remove the model driven app, and only keep the sitemap?

Yes, but dependency rules will still apply to any other components.

Query: Any links to articles explaining suggestions for solution development would be appreciated.

https://learn.microsoft.com/en-us/power-platform/alm/how-managed-solutions-merged#merge-navigation-sitemap-customizations

This document explains the merge behavior and even highlights what happens with conflicts, if any MS updates need to be removed. Then the editing approach comes back in. Remember that ultimately your managed solution will be on top of the MS solutions so trust that your customizations will take precedency.

Was this reply helpful? Yes No
Suggested answer

Alex Dan 365 73 on at

Like (1)

Report

Hi Nicholas,

For future projects, consider creating a new model-driven app (from your solution) to have greater control over its components. During the creation process, you can opt to use an existing sitemap (e.g., the Sales Hub App) to avoid starting from scratch.

This approach allows you to have better control over the UI/UX, ensuring a consistent and customized design for your app.

Additionally, it gives you more flexibility in managing your pages, and you won’t be affected by unexpected sitemap changes from Microsoft (like the addition of new features such as the Copilot page in the navigation).

Was this reply helpful? Yes No