Chris Haley Solution Architect

We have a client who regularly provides for bi-weekly working patterns for their employees,

The simplest example would be 'I don't work every second Friday' but could have much more complex patterns that repeat every two weeks.

It is a tedious manual task to configure this type of pattern because the working hours setup for a bookable resource only supports weekly rules.

Please could you add support for biweekly patterns.

Dynamics 365 Finance provides a feature called 'Accounting Source Explorer' which allows a finance user to look at a set of voucher transactions in the GL and have information from the source document displayed in a single view. This is useful for reconciliation and can be exported to Excel to pivot and identify transactions which are contributing to a balance. In standard, information from source documents is provided for customer and supplier invoices and expense reports only.

It could be incredibly useful to include the transactions that are posted from the Project Operations Integration Journal as a source document. It should apply to all transaction types (Hours/Expense/Fee/Materials) and fields could be included such as Project ID, Task ID, Worker ID, Resource name, Transaction category name, Chargeability, Quantity, Transaction date.

For an organisation with a large number of legal entities, the periodic revenue recognition process requires a lot of repetitive actions in each legal entity. It would very useful to have 'global' versions of the batch jobs 'Create', 'Delete', 'Post' and 'Reverse' revenue recognition.