Comments
While using ConfirmationDialog u expect the user to confirm something, so the expected behaviour is to have all the groups expanded by default. So my Vote is YES.
But ConfirmationDialog is being "deprecated" in use, so its normal that the request will not get more votes.
If u need a field and u want it visible, u just throw it off the group and didnt use groups directly. For me it's a bad procedure, i want to have a header in the confirmation dialog, and i cant without a group, but i cant request the usre to input me something that is hidden by default.
I would rater preffer the groups being collapsable or expandables by programation.
Sadly i dont think this idea will get accepted, cause the low use of Confirmation Dialogs.
Of course , we have reports to use with request pages.
Sadly we need the reports, and we cant use reports just to request data to users, so reports are a no.
Solution: no header and no groups in confirmationdialogs
@Jason Green You need to provide an update on this. The poor user experience your change has introduced is now three years+ in the making and STILL no resolution or response. Please provide an internal ticket number or DevOps task that we can reference going forward, your silence is deafening considering this is such a critical problem. There are 650+ votes on this spanning three separate requests:
This request:
Bring back the Breadcrumb menu
https://experience.dynamics.com/ideas/idea/?ideaid=752864bc-6657-e911-b047-0003ff68ea4d
105 votes
This request:
Make D365O breadcrumb clickable as in Windows Explorer
https://experience.dynamics.com/ideas/idea/?ideaid=f2c2d57b-ec19-e711-80c0-00155d460d59
527 Votes
And this request:
Keep breadcrumbs enabled in all future upgrades
https://experience.dynamics.com/ideas/idea/?ideaid=69893b08-b855-e911-b047-0003ff68b3fd
37 Votes
We need navigation, we need CLEAR navigation, and we need the ability to help support our users. There is nothing "lost" by giving people a menu path of where they are. I'm sorry this isn't how your marketing department wants users to use the tool, and I know your engineers have their own idea of how they want business to operate their ERP systems, but sometimes design and reality are not always in sync. Dynamics is not Word, and Dynamics is now PowerPoint. This is an ERP system which is inherently based on menus and hierarchy. Please provide an update ASAP.
Yes, such duplication leads to hard work for developers, or such pages going out of sync with the 'normal' ones. Plus, it can be better handled by extending the standard page with 'modes', e.g. by adding a `procedure SetSubcontractingMode(Boolean)` or adding a `RunPageView` filter, then detecting those and adding/hiding fields/filters/etc. I have done that to remove/replace 'duplicate' pages in the past, and I think it worked fine.
Yes, you should implement this, please. :-) Generating permissions for all objects added in an extension is extremely useful, at least during initial testing phases and as a starting point for more refined permission-sets. There has been a way to generate them until the change in format, and there should be a way to generate them after that. Thanks!