Al: Contols to extend standard pages hard to understand

Created on 10 Jan 2018 · 5Comments · Source: microsoft/AL

When creating page extensions for pages like the Order Processor Rolecenter or Purchases and Payables Setup the existing controls are numbered instead of names.

Is this going to be changed? The problem is that if the answer is yes, you guys are going to break my extension...

question

Source

markbrummel

Most helpful comment

I vote changing it into more understandable names. We are just at the beginning of extensions. How are you going to explain this to someone new to nav?

markbrummel on 10 Jan 2018

👍3

All 5 comments

We are aware of this problem. Unfortunately C/SIDE never forced developers to put a name on their controls & actions. The poor naming is already a problem in C/SIDE when write page tests.

We don't have a plan on how to handle this yet. There is no imminent plan for renaming the base-app.

On one hand we would like to have meaningful names on controls/actions, but on the other hand we don't want to break anything. Not an easy one.

esbenk on 10 Jan 2018

I vote changing it into more understandable names. We are just at the beginning of extensions. How are you going to explain this to someone new to nav?

markbrummel on 10 Jan 2018

👍3

Definitely +1 for changing the names into something sensible. This will be MUCH more painful to change in the future, when there will be a lot of extensions out in the wild.

vytjak on 10 Jan 2018

as well as in other topic I am definitely for breaking hard with the old way. In general, it would be nice to leave numbers and ids out of development altogether. Numbers don't only look like crap, they can't be memorized and lead to problems in the future. See the conflict topic in the individual number range of objects.