Finance | Project Operations, Human Resources, ...

Naming convention for grid control

(0) Share

Report

Posted on by Prasanna Munasinghe

The most effective naming convention for a form grid would be to use the name of the data source. This allows for easy identification of table field names directly from the dashboard without needing to open the form at the design level. This approach simplifies troubleshooting processes significantly.

In this scenario, control names are manually adjusted by adding a prefix derived from the data source name. However, if the grid name is assigned initially, these control names would be automatically generated accordingly, eliminating the need for manual adjustments.

My suggestion is to leverage the benefits of assigning meaningful names to grid controls. Do you have any thoughts on this?

All responses (3)

Answers (0)

Mohamed Amine Mahmoudi 10,150 Super User 2024 Season 2 on at

Like (0)

Report

Naming convention for grid control

Hi,

Thank you for suggestion, but i think you can post your suggestion in Dynamics 365 application ideas site.

https://experience.dynamics.com/ideas/

Best regards,

Mohamed Amine MAHMOUDI
Suggested answer

Kevin Xia Microsoft Employee on at

Like (0)

Report

Naming convention for grid control

Hi,

This is indeed a good idea. Using the data source name as the control name provides clear identification and improves the overall user experience. When viewing a form, users can quickly identify relevant data sources and table field names, thereby improving work efficiency. If there is a problem with the data or there are other failures in the system, this control name also allows the problem data to be easily traced, speeding up the problem resolution.

Best regards,

Kevin
Martin Dráb 230,354 Most Valuable Professional on at

Like (0)

Report

Naming convention for grid control

I'm not sure what you're trying to say and whom do you address the suggestion to. Are you trying to make a feature request to Microsoft? If so, please use Ideas.

Which scenario is "this scenario"?