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.


Hello, this is Gregg.

Thank you for your valuable feedback and suggestions. I'll inform our backend team about this and we'll consider to improve our product with your ideas.

Best regards,



  1. Using payment days and payment schedules we can define fairly flexible payment calendars in multiple installments.
  2. 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.
  3. As a concrete example, it is typical in the agriculture industry for customers to start paying only once the harvest starts (specific month).
  4. ------------------------------------------------------------------------------------------------------------------------------------------------
  5. In addition in this feature, it would be useful to have a range of months where the start month is applicable.
  6. 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. 
  7. 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.


In Budget Planning form in D365 F & O, there is no mention/Field of main account description and only the main account codes are appearing.

So, it's the valid ask from business users to publish the main account description beside the main account code as shown below-


Business need Business unit dimension values to be forced on all accounts and in all transactions due the Business unit is primary reporting attribute. By using account structures, we can achieve this by making Business unit as mandatory financial on all main accounts. 

But in sales order and purchase order we need to split/Distribute the Accounts receivables and Accounts payables respectively as per the dimensions on each line of sales/purchase orders. 

For purchase orders and Accounts receivables free text invoices we can achieve this by updating the parameter in general ledger modules: 

Values used for summary account= Accounting distributions 

Gap is on Sales order; the above parameter will not distribute sales order header as per the sales order lines dimension. 

There is an existing Idea on this.



The department field is available as a part of Graph API and also if you use Office 365 Connector - Get User Profile v2 connector to retrieve profile information, it can make 'Department' field available as well.


This would be amazing! Pretty sure this is standard functionality in Oracle!!!


this is already available using the professional tools


Great idea!! We did this with a customization but would love to see it as standard functionality.


  • 1
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 500