Public Profile
  • 'Edit' or 'Card' shortcut on fields with tablerelation to ease navigation to entity CARD

    When setting a TableRelation on a field, the field is shown on pages with the LookUp and Advanced Lookup options. (or 'Select from List' in the WebClient / BC) This allows the user to easily select a new record / value from the dropdown list or from the LookupPage. This is ideal for entry of new documents. However, once a document has been created and a value has been assigned to a field, it often occurs that an end user wants to get more information about that value, by opening the CARD page. Currently, the user needs to perform minimum 2 clicks. Either use Lookup > Advanced (to show the list) > Edit (to open the card). Either using the Advanced Lookup (to show the list) > Edit (to open the card). Our request is to provide a direct 'Edit' (or 'Card') option on fields with a tablerelation (with shortcut), so when a field has the focus, we can immediately open the card of the field involved. There are alternatives by providing a custom assist edit, custom 'Show xxx' action (e.g. 'Customer' action on Sales Invoice), provide a factbox with limited information, ... but having an overall 'Edit' option on the fields having a tablerelation would ease the navigation of the end user.
  • Enlarge 'Unit of Measure' description field to 30/50

    All master data / setup tables in NAV having a description field, allows description lengths of at least 30 to 50 characters. Only the 'Unit of Measure' table still doesn't follow this pattern and is still limited to only 10 characters. Since we're not able to extend this field via an extension, can we have the description field length (and translated description) updated to 30/50 by MS?
  • Data Replication feature / advice

    Having implementations with tens of companies in a single database puts some challenges on the part of master data management. Often most of the companies share the same setup data (post codes, unit of measures, ...) or master data (same customer base for a group of companies). Using RapidStart packages is good for initializing a company, but when data is changing, updates needs to be transferred to all other companies. Having some native features available (instead of external/internal tooling + avoiding additional licenses / costs) would certainly ease the maintenance of data from WITHIN BC. If not possible on short-term, some guidelines / best-practices are appreciated as well. (using external Excel sheets together with Soap UI and webservices, using RapidStarts sheets in combination with PowerShell, using Workflows in combination with data definition framework, using MS Flow ...)
  • Easily apply / type new filters on report request page

    One cool thing about the upcoming PAGE filtering feature is that we will be able again to 'type' (search) a field name we would like to filter on, instead of selecting by mouse. Can we imagine similar behavior for the REPORT request page filtering as well? Being able to just type to search for any field name, and type to apply a filter value (the same way we were used to in the Classic Client), will speed up the process (instead having to scroll and using the mouse). PS: I'm currently also struggling with finding out how to add a filter on an extra field as an end user, not part of the request page ...

  • Updated search behavior, propose Dropdown when multi record match?

    Suppose you have 2 customers that are named 'Van Terp A' and 'Van Terp B'. When users enter the value 'Van Terp' in a 'Customer No.' / 'Customer Name' field (e.g. on the sales order / sales invoice), the customer dropdown list is shown after 1-2 secondS, so (s)he aware of multiple results and can select the correct one. All Ok, as long as the user is patient to wait for the dropdown to appear ... Since it concerns a Power user (coming from NAV Classic) that is actually used to input complete documents in seconds, (s)he doesn't wait 1+ seconds for the dropdown to occur and presses ENTER / TAB to continue to the next field. This results in BC always taking the first valid value instead. They need to have patience for the dropdown list to load first, then select the correct customer and enter / TAB. This takes approx. 1 - 2 secs to load, which is too long for these users. Can this be enhanced so the dropdown is at least shown in case multiple records apply / results are returned by the search query? We used to create our own Search function all over our addon to provide this behavior, but it would be far more better if MS / BC could provide better native support.
  • Respect color / StyleExpr of 'selected' line

    In the BCoP release, seems like colors are no longer shown in the WebClient for selected lines / cells. The Windows client does show all colors, even when selected. Can this be fixed? Also see https://www.yammer.com/dynamicsnavdev/#/Threads/show?threadId=1184369009
  • Provide better support for e-mail fields with 'ExtendedDataType'

    - The 'mail envelop' icon on the customer card page on the latest BCoP seems no longer available. So the 'ExtendedDataType' property seems no longer supported in the webclient. 2 enhancements: - Provide support for the ExtendedDataType (esp. 'E-mail') in factboxes. This would allow one-click mailing. - Be able to override the behavior when clicking on the 'Mail' icon. This would allow us to customize the mail to be sent (e.g. applying a mail template) I know the above can be achieved by adding an action 'Send Mail' to factboxes as well, but the 'Mail Envelop' icon looks more intuitive and can easily be implemented across various fields / domains. Also see https://www.yammer.com/dynamicsnavdev/#/Threads/show?threadId=1179552534
  • Allow to override the 'New' behavior

    We would like to be able to override the 'New' behavior in the webclient. From within a list page containing all kinds of 'Orders', users can create new orders / edit orders. However, we've introduced some kind of 'order templates' that show an order via different types of pages (basic order / extended order / import order / export order / ...) each having their own set of fields. When creating an order, users first needs to selected an 'order template' (runmodal list), before the actual order page is shown. When the order page is shown, it should open in new mode. The same applies when opening an order card. The CardPageID is not sufficient, since it depends on the order template. However, this could be managed via the PageManagement codeunit.
  • Rendering of page with pageparts containing multiple groups

    We often use page parts to reuse a set of fields on different pages. When pageparts contain multiple groups, the groups were rendered below each other in the Windows Client. This did not give the best results, since a lot of white space was unused. In the Webclient, the result is somewhat better, since the columns of both groups are horizontally spread accross the screen size. However, it would have been better to show the groups next to each other instead of below each other. To put it in other words: when the groups of the page part are copied to the source page as normal groups, all renders well (next to each other). When moveing the groups to a pagepart, the rendering is applied differently (below each other).
  • Open page in FULL screen mode

    When I navigate to a page that is opened in View mode, the full screen size is used (no modal pages are shown at this stage). When 'Edit List' is used, the page is modally opened (pages are stacked on top of each other) and the page is no longer making use of the full screen size. Can we 'maximize' pages and extend them to make use of the FULL screen size?