-
Improved UX for code fields and name/description flowfields.
We have lots of pages that are overloaded with controls, forcing the user to scroll to see information. Lots of the controls are actually a reference to a master table (code field) and the description / name of the selected record (text flowfield). It would be nice to have an application-wide feature allowing to use one control to input the value (based on the code field, using the current dropdown / search features), but to show the text flowfield as a result. The same way the 'Sell-to Customer Name' field on the sales documents acts, but without having to custom-code the whole thing. (although this actually uses a 'real' customer name field, whereas we don't want to add the option to overwrite the customer name.) This would save quite some space on pages. PS: In addition, it could be interesting showing only the flowfield in list pages as well, but when the user filters on the flowfield, to use the source field (code field) instead to execute the query. https://www.yammer.com/dynamicsnavdev/#/Threads/show?threadId=1147933144 -
Restore possibility to collapse factboxes and show promoted actions on factboxes
In RTC we had both of the options below on factboxes, whereas in webclient this seems no longer available, which is a step backward. - Collapsing of factboxes (seems not yet supported in BCoP) - Promoted actions that appear on factboxes (they are no longer promoted and are one click further away in BCoP) https://www.yammer.com/dynamicsnavdev/#/threads/show?threadId=1174614754 -
Provide better support for coloring an entire row on pages
We frequently make use of the 'StyleExpr' property to colorize an ENTIRE row on LIST pages. This makes it really visual to the end user if a line needs action / is blocked / is selected / is expired / what the status is / ... The developer is now forced to set the StyleExpr on any column, which is fun if the page has lots of columns. If a new column is added, it is often forgotten to apply the same StyleExpr. However, if the end user / consultant will use the webclient 'Personalization' mode to add field, these fields would not be formatted at all. Would it be possible to add a 'StyleExpr' property on row level (e.g. on the 'Repeater' control) as well? If no StyleExpr is set on the individual control, it would inherit the StyleExpr from the parent group. This would save us some time and newly added columns would benefit from it automatically. https://www.yammer.com/dynamicsnavdev/#/Threads/show?threadId=1224536699 -
Remove test on 'Code' field in Post Code table (African countries)
The OnValidate trigger on the field City in table 225 contains a test on 'Code'. In certain (African) countries there is no postcode and only the City field is registered. Please remove this test, either provide support to omit the test via events. https://github.com/Microsoft/ALAppExtensions/issues/1017 -
Print non-posted sales credit memo (Draft credit memo)
BC contains an option to print a non-posted sales invoice, using the Draft Invoice action, or the Pro Forma Invoice action. (unclear about the difference between both actions). In the report selections, usage options 'Draft Invoice' and 'Pro Forma Invoice' are available. However, for creditmemo's no support is available. Please provide (extensibility or native) support to print non-posted sales credit memo documents (Draft credit memo) Technical: we cannot extend this, since the 'GetSalesDocUsageType' in T36 returns 'CreditMemo' which is used in T114 to print POSTED credit memos instead ... -
Add 'Mobile Phone No.' on User Setup
It would be nice if we could have the 'Mobile Phone No.' logged to the User Setup (next to the current 'Email' field we have). This would allow sending authentication, notification, ... related stuff by SMS to the user. The same like we have the 'Mobile Phone No.' field already on customer, salesperson, employee, ...
-
Disable webclient animations
It would be interesting if the webclient / service tier could have a setting to disable all the (fancy) animations / sliding transitions between pages / opening - closing fasttabs. This looks nice but slows down the navigation process / UX, especially for experienced users / users needing to do fast data input. On Yammer, you can find a capture for a local on-prem environment with sufficient CPU / memory, showing the delay when opening / closing the fasttabs. Seems like this could go a lot faster when animations get disabled ... https://www.yammer.com/dynamicsnavdev/#/Threads/show?threadId=89236307689472 -
Re-enable multi-level tree list support in Webclient (ShowAsTree / IndentationControls)
Windows client provided support to build 'dynamic' pages using collapsing tree views. Collapsing / expanding tree nodes was userfriendly, since it limits the information shown when loading the page and allows to user to decide on what node / level information was needed. However, since the move to the Webclient, collapsable tree views seem no longer supported, since the ShowAsTree and IndentationControls properties behave differently. https://docs.microsoft.com/en-us/dynamics-nav/feature-limitations-of-the-microsoft-dynamics-nav-web-client Please re-enable collapsable / multi-level tree list support in the Modern client. Preferably with extended with the option to collapse / expand per level (1 / 2 / 3 / ...). Cfr. the experience Azure DevOps offers in their Backlog overview to show work items with/without childs.
-
VS Code - "Go to 'Object' Definition" vs "Go to 'Variable Declaration' definition"
When developing in C/SIDE, the 'Go to Definition' on variables with a complex datatype (pages, tables, codeunits, ...) always opened the 'object'. It didn't point to the variable declaration (globals / locals) Working in AL with the 'Go to Definition' always navigates / points to the variable declaration first, from where we need to click a second time on the datatype to actually open the object / file. Please provide VSCode alternative to allow direct navigation / Go to 'object' definition, the same way it was implemented in C/AL. recCustomer : Record Customer; recMyISVTable: Record "MY ISV Table" ... recCustomer.MODIFY; >> Alternative would be appreciated to open the 'Customer' table when right-clicking on the recCustomer. recMyISVTable.whatever; >> Alternative would be appreciated to open the 'MY ISV Table' table when right-clicking on the recMyISVTable. -
Dynamically change the CurrPage.Editable property at runtime
We would like to provide proper user experience to prevent modification of records in certain scenarios . Following the thread on Github, we are trying to allow certain users to change data based on a status and others not to (or all users not to change data after a certain status is achieved). So it is necessary to be able to change "Editable" of a page on runtime. See https://github.com/Microsoft/AL/issues/1664 for more details.
You’re offline. This is a read only version of the page.
