Can you please make all related table fields available to users to be added via personalize vs having to create an extension to add existing stock fields to pages. This way customers can add fields they need without having to pay a partner to write and add an extension to add fields to pages.
Good news! others have had similar ideas so we're merging them into one.
Here's what Chad said in his idea: "I would like to be able to add the Document Date or Posted Date as a column in the Posted Sales Invoices table view screen. When personalizing, Document date is not an option to choose from, it would be nice to be able to add more column in more areas. Seems very limited."
Under review but needs more votes!
The final solution would likely need to give developers more explicit control (eg. a new AL property) to specify which fields *cannot* be shown via personalization.
To be consistent, all fields in eg customer ledger entries should be made editable no, else the would be editable in the list (ok, it would not be saved).
What about cases, where Qty. to Invoice will be added to the sales invoice subpage, and changed? (Qty. to invoice must be editable for orders, so probably such cases must be solved by Code?)
Please also ensure to exclude hidden (flow)fields in the query. Also a rowstyle property would be nice, since we often tend to colorize all columns/fields based on a given status.
Ideally we should be able to exclude certain fields (property 'Internal'?) to be added to pages by the user, if they had been (mis)used for internal / coding purposes only. Sometimes we add a temp field to a table to transfer data when applying the arguments patterns, but those fields should not really be used / shown to the user.
CAn I get an update on this? It appears this idea was lost in the shuffle
Business Central Team (administrator)