Dynamics 365 Layout

Hi, Is it possible to add an option to view the dataset of a report? A lot of consultants and end users use Word layouts to customize their own reports. This option was available in previous versions of Dynamics NAV as a hidden feature in the layout preview of a report and was extremely helpful. Thank you! Kind regards,

After transitioning to UCI and starting importing data, we wanted to access the "Imports" so that we could see the results of our imports. We tried to add the button to the "Site Map", but we were unable to. It would be nice to have the "Imports" button be in the UCI. Thanks,

I want to be able to open records in new tabs either from the right click menu or the middle mouse button

Pegging area is located under Related information, and is not very user friendly - or of no use. Pegging area should be located in the bottom of the screen instead.

There is an issue in Dynamics CRM with SiteMap order, there is no way to set the sequence of the SiteMap area items. When importing a few solutions with sitemap changes, if there is a sitemap conflict it will put the sitemap area at the end of the sitemap. There should be a sort order value that can be set so you have full control over the order of the sitemap areas. When there is a conflict it just puts the area in the next available so there are inconsistent results over multiple Dynamic CRM deployments

In the current Index optimize Job is it possible to modify only four settings: - DTU Threshold - Duration (maximum) - Index Quantity (maximum) - Online / Offline index rebuild Especially short after a Go-Live but not restricted to this moment do we notice huge quantities of heavy fragmented indexes. This is not a situation we would like to see, they are caused by mainly three fixed parameters. There is first a index usage threshold of 10.000 (formula unknown) together with a threshold of 50 % fragmentation level combined with a page count Level of 100 and a usage The second is a threshold of 25 % fragmentation combined with a page count Level of 200. Incase a certain database growth is not established or when cleaning/archiving is done frequent does this lead to unexpected high fragmenation levels. Many customers / database administrators and technical consultants would benefit from a small change. This would be the addition of three additional parameters. - Manual override of the usage threshold of 10.000 (checkbox) - Add a new parameter 'page count level', field type integer and I advice a value between 5 and 200 - Add a new parameter 'fragmentation level', field type integer and I advice a value between 10 and 99 Thank you very much for your attention, it will make customers happy around the Globe! Martinus

Frequently it would be helpful to be able to display forms within model-driven apps either as a grid/table or by using nested form elements. Having the option to align fields to a grid sometimes gives a more user-friendly look. Other times it would be helpful to nest a two-column section inside a column of another section. For example, if I want to show multiple subtasks within a parent task, being able to nest them inside other elements would make a far more intuitive UI, and could allow for business logic to mark the parent task complete when the subtasks are completed. Perhaps capping it at one nested level would add functionality/UX to the forms without creating excess levels of complexity?

The inline lookups (the ones that open the table on the same page, under the textbox) have an "aria-expanded" attribute that behaves different on card pages vs tables. On card pages that attribute gets stuck on true after opening the lookup the first time. I would expect this attribute to return to 'false' once the lookup table is no longer visible (this is the behavior on tables). This is not really an idea, so please point me in the right direction if I should report this somewhere else.

Removing the ALL feature from the powerbi app would improve the use and functionality of the app. Working in a dynamic health care setting, there are many departments that have sensitive information they do not want to share with other departments/individuals throughout the facility. I've done a lot of testing with individuals in our organization by adding them to a specific audience, only to see that they can still access all the reports loaded in the app. Because of this function, many departments do not want to utilize the app, requiring we share individual reports through teams. I read through questions and answers on the intranet, and see it's a systemic issue among analysts and developers.