-
Cursor default position on Return Order does not default to 'Item Number' field
The default cursor position when creating a Return Order via the Retail > Customer Service does not start on the 'Item Number' field but starts on the 'Quantity' field. 1) Navigate to Customer Service Menu 2) Find Customer 3) Select 'Return Order' 4) Select OK This behavior is not consistent across the different D365 modules as it does not occur when using the Accounts receivable module to create a Return Order. D365 defaults to the 'Item Number' field via this module. Impact: Negative user experience. Users must navigate to 'Item Number' rather than the form loading in a position of readiness.
-
Block users from changing personalizations & workspaces (but keep whats been imported for them)
We want to be able to create a suite of peronsalizations and workspaces for a group of users but then prevent those users from making any further changes to those peronsalizations and workspaces. D365 currently does not appear to allow this functionality. When de-selecting 'Personlisation allowed' against a specific user (Via system admin > Setup > Personalisation) that user loses all personalisations and workspaces created for them up to that point.
-
Improve erratic Sales Order form grid behaviour
SR Number: 119052425001510 Setup: Generate a new Sales Order. On the Sales Order form set the following: 1. Collapse the Action pane 2. Minimize the Sales order header 3. Maximize the Sales order lines 4. Minimize the Line details This setup is in-order to view as many Sales Order lines as possible on the grid. Repro Steps: Add lines until approximately 25 products on the sales order. Continue to add lines by using down arrow to generate a new line and entering product code followed by enter then down arrow again. Repeat steps observing grid behaviour. Symptom: The grid will start to behave erratically, jumping up and down intermittently at the point of adding a new line. Typing the next search item whilst the grid is mid 'up/down' motion also seems to trigger a search without it having been requested. This behaviour has been observed in a Contoso environment with PU26. Hugely negative impact on user experience as part of standard D365 sales order creation process. Idea: Can this erratic functionality please be improved ASAP.
-
Extend Credit Limit type to include Balance+Confirmation
Could you please extend the Credit limit type functionality in Sales ledger parameters to include one that is Balance+Confirmation. This would mean a customer available credit limit is only reduced at the point a Sales Order has a confirmation journal created and the document status changes to confirmed. Currently only None, Balance, Balance+All and Balance+delivery note or product receipt are available options. This would make our Credit Control departments life much easier when checking to see if a Sales Order can be released from hold when multiple open sales orders exist.
-
Total 'Row/record count' button - it would be very useful to see how many rows/records are in your table at a given point
Can you please introduce functionality that readily provides a total row/record count of any given table? Currently, a user must filter the table they are working on based on their given criteria and then export to excel to get this information. E.g. We finished your export of 22 rows. If this information could be visible without exporting or a single button could be pressed which would calculate this total, it would be extremely useful and save on a lot of unnecessary time exporting into excel. This seems like a simple concept. I look forward to hearing from you. -
Introduce select criteria to 'Recalculate credit limit' batch task (SalesCreditLimitCheck)
The 'Recalcualte credit limit' batch task does not contain the option to select any criteria to limit which credit limits or Sales orders it impacts.
Could you introduce a select option?
That way you could select a specifc customer or customer group.
Class name : SalesCreditLimitCheck
-
Add the in credit management field (CredManInCreditControl) to the Sales Order Headers V2 data entity
The data field in credit management (CredManInCreditControl) is not available on the Sales Order Headers V2 data entity despite being on the GUI view.
This is key piece of information regarding if a sales order is on credit hold can only be viewed via the GUI and cannot be reported on using any data entities.
Please add it to the Sales Order Headers V2.