Richard BLANC

In the asset event history we can see Old value & New value if we changed the asset code, but when we install the asset to another functional location the event history displays the new functional location and the dates but not the former functional location. We have to scroll this screen and look at the type of change to find its previous value. Could you please add this information directly?

When we move an asset to another functional location we can select a date for this change, but when we rename an asset its effective date is today. It could be helpful to synchronize the two changes (my customer would like to code the assets based on the hierarchy).

Microsoft pushes customers to use several D365 apps and says they are fully integrated, but if an employee is wrongly created in HR with upper case for example and later corrected, this update doesn't get into FO because the data management import is not case sensitive, so finally customer has to manage 2 databases...

Work order journals are posted into a project. There is an expense journal in AM, but in Project module when it comes from Asset management, it doesn't contain everything like an expense journal directly created on a project and it cannot be directly used to reimburse the employee. It is great to see expenses on a work order and to be able to bill it to the customer through the project but it would be better to also be able to reimburse the worker.

When a company A sells goods thanks to a direct delivery from an intercompany supplier, customer service team in company A would like to tell the vendor how to group picking and deliveries. Currently they can release "Intercompany picking" one by one, but this option is greyed-out when they select several sales orders (even if they share the same customer, the same delivery address and the same delivery date).

Today when we run Update worker periods with start date = employment start date, if the employement start date is not the start date of a period the system will generate periods after the employement start date. The consequence is the employee has no period for his first few days. This doesn't prevent timesheet posting but the times entered for these days aren't stored in « ProjPeriodEmpl » table, and of course they can't be seen from the Period status screen of the employee. Instead this function should generate periods starting with the last period BEFORE the employment start date. Example: employment start date is November 18th but periods start on 16th and 23rd. Current behaviour is to start with period on 23rd, but it should include the period starting on 16th so that times entered between the 18th and 22nd of November are correctly recorded.

The new feature to create recruitment request and candidates is nice but we should be able to link one candidate to several recruiting requests.

Despite the documentation placing "Schedule workload capacity" under Warehouse management (and not Inventory management) this functionnality cannot be setup for a WHS warehouse. When a customer uses WHS it usually means that logistics is a big deal for them: so they absolutely need a way to track their space utilization (and intbound/outbound planned workload).

Currently we can define Sellable days from the customer card by Item groups. Unfortunately these groups are the same as the ones in the Cost management fasttab of the item. There is no reason why Sellable days should follow the accounting posting rules so these two groups should be split (ie ability to define Sellable days item groups as there are Rebate item groups for example).