A quick refresher: saved views enable users to save sets of personalizations on a given form. Forms have a standard “classic” view. When personalizations are made, an asterisk identifies that the classic view has changed, providing the user with the option to save the new view.
In manage my views, users have the option of reordering, renaming, and setting the desired default from their personally available views. Additionally, the publish button in manage my views allows users to share their views with the larger organization by role and legal entity.
(The ability to publish views is limited to system administrators and those with the “Saved views administrator” role)
Publish as Default View
Platform Update 33 extends the publish view functionality, the publish as default view toggle enables a published view to be the first view a user sees when accessing a form – instead of the form opening in “Classic view” and the user having to select the desired view or configure the default individually.
In the example below, I have a “Simple view” for the project form where infrequently used buttons and fields are hidden. I would rather users be direct here first, with the option to view the full “Classic view” information if necessary, so I have published the “Simple view” as the default.
Managing Published Views
All views are visible in the personalization form. Clicking the publish button on a published, unpublished, or personal view allows management of access and presentation of the view.
I would be grateful if you take a screenshot of this post and share it on social media. You’ll be publishing a view – saved from my published, saved view on saved view publishing.
Grouping brings some pivot table-like functionality to D365 grids. Similar to how numeric columns can be totaled, non-numeric columns can be grouped. Right click on the column and select “Group by this column”
Posted Project Transactions, Grouped by Project Name
Posted Project Transactions, Grouped by Date
Save Groupings as Views
Once grouped, these new grid layouts can be saved as views.
Grouping is a promising UI experience. In the Platform Update 33 preview, users are able to group on a single column. Future plans include the ability to group on up to five different columns, expand/collapse groupings, and group subtotaling.
If You Still Really Want a Pivot Table
If you find yourself in need of the full pivot table experience, remember that grid data can still be downloaded to Excel.
What’s the sum of this column? No need to dump it to excel anymore – right click and select “Total this column”. D365 will then do the hard work to calculate the total and return the number of rows.
Even Large Totals!
When a grid is so large that all records are not returned at once, a calculate button presents below the total button with dashes at the bottom of the columns pending calculation. Clicking the calculate button processes the totals.
When grid columns are filtered, totaling takes place on the filtered values. This is handy when investigating subsets of form data.
In the example below, the Trial balance form already has summary totals at the bottom as part of its standard design. By adding column totals, I am able to filter for a specific project dimension and quickly calculate the totals for that dimension value.