Move and Hide Fields – Personalization | D365 Platform

Bill And Ted 3 Officially Happening With Keanu Reeves And Alex Winter Returning
So-crates, from Bill & Ted’s Excellent Adventure (1989)

Let him who would move the world first move himself” – Socrates


Rounding out this personalization series, let’s take a look at the move and hide features.

I think these two features should be more widely utilized. D365 forms are designed for multiple personas / business processes. Decluttering forms for specific personas by moving less frequently used fields farther down the form or hiding them completely is an easy way to increase day-to-day efficiency, as well as simplify the training/change-management process.


Move a Field

Open the personalization toolbar Ctrl+Shift+P and select the Move button. Click on the Field, Field Group, or FastTab to be moved. From there, drag with the cursor or use the Arrow Keys to indicate where the form element should go. I find using the arrows a bit easier to control. An orange indicator line displays where the form indicator will go, and Enter will set the field in its new location. Close the personalization toolbar to view the result.

Moving the Responsible field group to the end of the General FastTab.
Note the highlighted indicator line.

Result after closing the personalization toolbar.

Move can also be used to adjust the column order on a listpage.


Hide a Field

The hide feature works similar to the move feature. Hide can be applied to Fields, Field Groups, or FastTabs, as well as Tabs, Groups, or Buttons in the form’s header ribbon. It can be done through the personalization toolbar, or by right-clicking, selecting personalize, and then selecting Hide for the desired form element.

Right-click, Personalize, and Hide the Project team and scheduling FastTab.

The FastTab disappears from the form.

But Where Do Hidden Fields Go?

Dust. Wind. Dude. …Woah.

No, the fields aren’t lost forever. Using the Personalization toolbar, click on the hide button to reveal which form elements have been hidden through personalization.

Some parts of the Projects form are hidden, but which ones?
I don’t have a photographic memory.

Open Personalization toolbar and selecting Hide
What was hidden is now revealed.

Create a New Field – Personalization | D365 Platform

Statue of Issie, Japanese Lake Monster

In 1955, Bernard Heuvelmans created a new field: Cryptozoology – the study of imaginary animals.


Create a New Field

As mentioned previously, when adding a field through personalization users also have the option to create a new field. After opening the personalization toolbar, selecting Add a field, and choosing the desired location for the added field, users are prompted to select from an existing field or Create new field.

In the Create new field area, users can define

  • The table where the new field should be added
  • The new field’s prefix (all fields added through personalization end in _Custom)
  • The field’s data type (Text, Number, Decimal, DateTime, Date, Picklist, Checkbox)
  • The field’s label
  • The field’s help text (what displays when the hovering the cursor over the field)

Example of new Picklist field creation

Example of new Checkbox field creation

Example of new Example fields displayed on Customer form


Additional Considerations:

In a few clicks, a new field can be created and added to a form – saving hours of developer time, code promotion, and testing over the standard approach of doing this through development. That’s good. But with the ease of creating a new field, don’t neglect thinking through the below – which could save headaches associated with implementing any new field – whether through personalization or development.

Access

Who needs to see or edit the new field? From what forms? Personalization can add the new field to the saved view, but the new view(s) will need to be published to the desired users or roles.

Data Migration

How will the current data for this field be loaded in D365? Who will do it? In System administration, there is a form to manage Custom fields. Here, a custom field can be added to a data entity for data migration. The Custom fields form is also where field values like picklist options or the length of a text field can be updated.

Reporting

Does this custom field need to be added to any reports? It is easy to add a custom field to a listpage using personalizations. Visibility on the listpage is frequently enough, and Ctrl+Shift+E can be used to quickly export listpages to excel.

Custom Example field on Customer Listpage

If the new field needs to be added to a formatted report, or to a data model for consumption in PowerBI or another reporting solution, you may need additional developer assistance.

Testing

One last thought about creating a new field through personalization – it doesn’t follow the standard QA->UAT->Production path of regular code promotion. A new field can be created as a test in a test environment, but at showtime a user has to create the new field directly in the production environment. This is probably fine for fields that are “just extra attributes”, but probably not fine for fields related to a company’s core business. If additional methods or logic need to be applied to a field, it is probably better the field be created through development.

Additional Reading
Personalize the user experience
Create and work with custom fields
No Developer Required – Adding Custom Fields in Dynamics 365

Add a Field – Personalization | D365 Platform

untitled, field, farm, green, grass, agriculture, tree, plant, nature, outdoor

When he went out to plough his fields…his heart would fill with joy.”

How Much Land Does a Man Need? | Leo Tolstoy


D365 contains thousands of related tables with an almost innumerable number of fields – some say D365 has almost as many fields as this blog has fans. But sometimes a user just needs one more field.

Users access this table data through forms. Frequently, a form’s standard view will not contain every single field of related table data. Did you know the customer table (CustTable) has 203 different fields? Add a field allows additional table information to be presented on a form.


Add a Field

Use Ctrl+Shift+P to bring up the Personalization Toolbar and click on Add a field. Once Add a field is selected, click on the part of the form where the new field should go.

A new “Add columns” area will pop up on the right allowing the user to select which field (or fields) to bring into the form. Did you know that 3 of the 203 fields on the Customer Table are notes fields?

The selected field(s) will now display on the form.

If the field isn’t positioned quite where intended, the Move button ca be used to fine-tune the location of the new field.

Add a Field, Again!

It is generally bad database design to represent the same field twice on the same table, but not necessarily bad form design. For example, it may make sense to have customer currency in the sales demographics FastTab, and terms of payment in the Payment defaults FastTab. It might also be helpful to have this information closer to the top of the form. Add a field could be used to bring those fields onto the general FastTab in addition to their standard locations.

Add a Custom Field

Observant readers will notice the “Add columns” area also includes a “Create new field” button. Links below are included to outline that functionality – I’ll add my own opinions on the pros and cons of adding custom fields through personalization in a later post.

Additional Reading
Personalize the user experience
Create and work with custom fields
No Developer Required – Adding Custom Fields in Dynamics 365

Personalize Lock Fields | D365 Platform

The ‘Loch Ness Monster’ is not that kind of ‘Lock’. Regardless, you want to lock monsters from ruining your system with bad data entry.


Lock Fields

In personalization, Lock allows users to view fields, but not change their values. To lock a field, right click, select personalize, and then check the lock button.

As with all personalization features, these locked fields can be distributed to other users as published saved views.


Can’t This Be Done Through Security?

Yes. Without personalization, controlling who can see or edit what fields is managed through security. If you click on security diagnostics for the Vendor form, you can see there are two security privileges: one to view vendors and one to maintain (edit) vendor data.

To lock down a subset of fields through security, a system administrator would need to create a new security privilege (or modified copy of the maintain vendors privilege) and assign it to the desired duties or roles.

An advantage of locking fields through personalization is that it is easier to see which fields are being locked through the UI. Also, users can have multiple views – It’s possible have a default view where the data is not editable, but allow the user to toggle to another view where the data can be edited. This would be a more difficult proposition to manage through security. Pro tip – if you care very much about tracking edits to a particular field, consider enabling database logging on that field.


Lock Many Fields

Personalizations can be applied to individual fields, as well as Field Groups or FastTabs. If you want to lock lots of fields on a form, the easiest way to do this is by opening the personalization toolbar, clicking Lock and then clicking on the desired Field Group or FastTab.

Clicking on the Payment group controls all fields in the Payment group

Clicking on the Payment FastTab controls all fields in the Payment FastTab


That’s pretty much the whole concept – Lock, Stock, and Barrel.

Additional Reading
Personalize the user experience
D365 security topics
Database logging

Personalize Labels | D365 Platform

Campbell’s Soup Can by Andy Warhol

You say ‘Tomato’, I say ‘Tomato’ ” …a phrase better sung than read. No matter what label you wrap around a can of tomato soup – it’s still a can of tomato soup. In D365, buttons and headers have labels. The flexibility of having labels allows D365 to be useable in 46 different languages (including 9 types of English!). All the buttons are the same, but each has a set of language-specific labels. Custom labels can also be created through personalizations, then distributed to individuals or groups of users through saved views.


Personalize Labels

Right click on the desired button or header and select Personalize.

The label name will appear in the white field of the personalize box.

This text is editable, edits will change the label presented to the user.

These personalizations can be saved as a view (note the asterisk after “Standard view” in the last image) and the view can then be used individually or published to other users as desired.


Is This a Good Idea?

Well, maybe.

Without personalizations, label changes are a development task. A developer has to update the label file. That code has to get promoted up to the production environment. These changes then affect all system users of that language Want a label for only some users of that language? – just create a 10th version of English…then have that subset of users change their language preference. Personalizations is clearly a lighter touch for changing the name of a button.

But what is the purpose of a language? Common language facilitates communication. When I point to a can and tell you “tomato soup”, it’s only helpful if you also know it as “tomato soup” (Gazpacho…What’s that?). If sub-groups start referring to something by a new name, it can be difficult to talk about it across the whole organization – or describe to support technicians.

If Bob wants to rename the “Adjust transactions” button to “Bob’s Oh-no Button,” and have that on his own view…good news! That functionality exists.

Bob will have trouble describing “his” button to other members of that organization that know it as “Adjust transactions” in the standard view.

Clicking Bob’s Oh-no Button will still take Bob to the same Adjustments form (remember, this is the same button for everyone, only being viewed with a different label).

However, if accommodating a special request like this can facilitate change management, or win Bob as a champion of D365 throughout his organization, the exercise might be worthwhile.

So, Maybe.

Additional Reading
Personalize the user experience
How to create a label in Dynamics 365 for finance and operations
How to create a new language in Dynamics 365 for Operations

Personalize Required Fields | D365 Platform Update

Photo: Charge of the Light Brigade by Richard Caton Woodville Jr.

For want of a nail the shoe was lost;
For want of a shoe the horse was lost;
For want of a horse the battle was lost;
For the failure of battle the kingdom was lost—
All for the want of a horse-shoe nail.


Little things matter. Sometimes little things matter a great deal. Adding required fields helps prevent little bits of data from being lost on the great battlefield of D365.


Personalize Required Fields

In Platform Update 10.0.12. Require has been added as an option to the personalization toolbar.

As long-time readers will remember, the personalization toolbar can be accessed through the option tab, or by pressing the Ctrl+Shift+P hotkey. Once open, the user clicks on Require, then clicks on the fields to be required, and then closes the personalization toolbar.


Saved Views

As Saved views, these personalizations can be published to the desired members of the organization through security roles (see Publish saved views link below in additional reading for more details).

In addition to being a no-development solution, an advantage to this approach is that different fields can be required from different users. Imagine a business process where a general projects team create new projects across the company, but project managers are expected to enter a projected start and end date for visibility once they are specifically assigned to and begin maintaining their project.

Requiring the field through a saved view makes it easy for the project team to create and update other elements of the project through a standard view, while the Project manager’s view requires these data points to be entered.

Project manager view requires project start / end dates

Error message for Project manager not entering required fields

With fields populated, happy projects are all the same.

Additional Reading
Platform updates for version 10.0.12 of Finance and Operations
Personalize the user experience
Publish saved views

Enable Saved Views

As regular readers know, Saved Views enhance the Finance and Operation experience, empowering users to save sets of personalizations and navigate forms more efficiently.

In earlier versions, this preview feature had to be enabled through SQL code – starting in Platform update 33, Saved views can now be activated in the Feature management workspace.

Go to Feature Management Workspace

If you do not see the Saved views feature, click Check for updates. Depending on how far in the future you are, you may also need to toggle from the “New” tab to the “Not enabled” tab.

Hello readers in the future. How is it there?

Select Saved Views Feature

Click “Enable now” at bottom right.

Saved Views Feature Will Now Be Enabled

A green check mark and enabled date will now display next to the feature.

When activating the Saved views feature, also consider enabling the Grouping in grids and New grid control features.

Additional Reading
Saved Views
Grouping In Grids
New Grid Control

D365 Platform Update 33 Preview: It Publishes Default Saved Views?

The preview release of Platform update 33 for Finance and Operations is now available (general availability is scheduled for March). This is part of a series highlighting features in the new platform update.


Published Views!!!

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.

One can only hope that will lead to more views.

Additional Reading
What’s New Platform Update 33
Saved Views
Saved View Feature Details

D365 Platform Update 33 Preview: It Groups!

The preview release of Platform update 33 for Finance and Operations is now available (general availability is scheduled for March). This is part of a series highlighting features in the new platform update.


It Groups!!!

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.

Ctrl+Shift+E, Enter

Our D365 hotkey to download data to excel.

Alt+N+V, Enter

Our Excel Hotkey to build a pivot table.

Then select your fields as desired.


Best of luck, my Excel power-user friend.

additional reading
What’s New Platform Update 33
Grid Capabilities
Grouping With Subtotals in Grid

D365 Platform Update 33 Preview: It Totals!

The preview release of Platform update 33 for Finance and Operations is now available (general availability is scheduled for March). This is part of a series highlighting features in the new platform update.


It Totals!!!

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.


Filtered 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.


In sum, this is the total functionality.

additional reading
What’s New Platform Update 33
Grid Capabilities
Total Recall