Comments
Some kind of workflow to control new product enrichment process is requested by most of the customers.Even better would be, if you could segment the required data by department, role or user (like suggested).Case management can be used, but it is lacking automation and controlling the process step-by-step (in predefined order; finishing previous step will trigger next step/activity automatically).
I totally agree with the above comments. It's really not a good user experience, because you need to check the time and attendance module, but mostly it's not used. So the preferred way would be, that it would be available if someone would use it otherwise it wouldn't be used and wouldn't be the key to run production floor execution, those two modules should be separated completely.
Using payment days and payment schedules we can define fairly flexible payment calendars in multiple installments.For example using payment schedule we can set the first payment to start next month, or two months from now. The feature we are suggesting is to have and additional option of providing a specific fixed month as the starting the first payment.As a concrete example, it is typical in the agriculture industry for customers to start paying only once the harvest starts (specific month).------------------------------------------------------------------------------------------------------------------------------------------------In addition in this feature, it would be useful to have a range of months where the start month is applicable.For example if sales is done between March and August, then the payment schedule need to start in November. From September to the next February it would revert back to currently existing functionality. It could be modeled as a base terms of payment with an optional alternate terms of payment. For example the terms of payment could be starting on a specific month and have an applicability range, and an alternate terms of payment when we are outside of the applicability range
Budget planning worksheet should be restricted based on the main account list of each user.The requirement here is if a user or group of user has restriction in accessing or viewing any main account in D365, then they are not allowed to view those main accounts which will be appearing in Budget planning form. For e.g. if a user is having restriction in a main account say 6XXXXX and then the user should not view this main account in budget planning form.