Dynamics 365 Project Operations

We have identified an inconsistency between Ledger and Project posting for certain type of adjustments. Specifically, we find different results on the ledger and project side if adjustments are performed after the exchange rate relevant for the initial posting has changed.

This issue is happening in item and expense transaction. However, in expense transaction, when adjustments are made after exchange rate is changed, it only affects the posted project transaction and not the voucher transaction. In case of item transaction, it does not affect the posted project transaction, but the voucher transaction amount gets changed.

Exchange rate change can happen because of one of the reasons:

• An actual change of the default rate (because of issues or agreements).
• Because the initial posting was made with a manually set rate (it is possible to override the system rate).
• Because of the 24 hours gap between the import of daily rates.

Customer Impact: This leads to an inconsistency in posted voucher transactions and affects their financials. There is no workaround for this as of now. 

Microsoft reference : https://fix.lcs.dynamics.com/Issue/Details?bugId=839678&dbType=3&qc=3e19c351be8cdf25365228d6a697702e9b006fe098b02cb40de0eaaaa41241be

Improvements related to Project Tasks - Please prioritize!

After contact with Microsoft in a support ticket I was asked to present my questions as a collection of ideas related to the same topic.

1)     The Project Task grid view columns should be possible to customize

• It is necessary to be able to add default columns to the Project Task grid on, such as Start Date, End Date, % Complete, etc. These default column settings should be added automatically each time a new project is created. It is very time consuming for Project Managers to have to adjust the grid view for each project, so this functionality is vital.

2)     It should be possible to customize the Project Task quick look window that opens from the grid on a Project

• There are certain fields, such as "Project Transaction Categories" and other Project Task related fields that are beneficial to see from the project task quick look window - without having to open the project task in a separate tab.

3) It should be possible to unlock or override the grey non-editable fields on a Project Task

• For a lot of projects the project tasks and sub tasks are not possible to outsource to a resource who should then enter time through time entries in order to update a project task.
• It has to be possible to choose if a project task progress (all the now grey fields) should be editable directly from the grid view or in the project task quick look window.
• Possibility to edit the progress of a project task directly by the Project Manager is essential, otherwise the system get's to complicated and users will not follow the processes if not all department and functions are not integrated to work in D365.

4)     It should be possible to add default Project Buckets that will always be set on newly created Projects

• This is essential for project management, and will otherwise be a very time consuming activity leading to unhappy users.
• It should be possible to create business rules etc setting the default Buckets based on a specific project type or similar.

5)      It should be possible to add default Project Sprints that will always be set on newly created Projects

• This is essential for project management, and will otherwise be a very time consuming activity leading to unhappy users.
• It should be possible to create business rules etc setting the default Sprints based on a specific project type or similar.

6)     It should be possible to add default Labels that will always be set on newly created Projects

• This is essential for project management, and will otherwise be a very time consuming activity leading to unhappy users.
• It should be possible to create business rules etc setting the default Labels based on a specific project type or similar.

7)     It should be possible to add default “Conditional Coloring” that will always be set on newly created Projects

• This is essential for project management, and will otherwise be a very time consuming activity leading to unhappy users.
• It should be possible to create business rules etc based on a specific project type or similar.

Please integrate the Microsoft Roadmap functionality with Project Operations in order for project managers and other related users to get a full overview of the ongoing projects.

The MS Roadmap view is very important to complete the possibilities and usage of Project Operations. When handling a large number of projects simultaneously it is vital to be able to align and structure projects by using this tool. I believe this could be very helpful and a large contributor for the product to work as intended and complete our needs as users of Project Operations.

When an employee posts an expense in the expense management workspace, he has the option to enter the transaction date of that expense. By default, the system assumes this date when the expense is approved and then posted.

However, considering accounting rules, the expense for the company should only be registered when the expense occurs for the company itself. This means that if an employee has a work expense in September, but only submits the expense report in December, for the company, the expense only should be posted in December and not in September (as the system does by default).

I suggest adding a new field in the expense report for the employee to enter the date on which he is submitting the expense or give the expense approver the possibility to define the expense date.

For Time entry records one can use the "Copy row" button on the grid to copy the Time Entry record. Please consider creating a similar button for Expense(msdyn_expense) records.

Advising with increasing the character limit allowed for the project ID

Currently, if a project ID is entered with more than 20 characters the system does not fetch the data assigned to that project ID and regardless of whatever the value that is assigned to that project ID, it appears as 0 value in the forecast report.

Hi team,

When entering negative amount in financial estimates for expenses on projects, estimates pricing is not updated unless pressing Update prices button in Estimates grid. It seems like negative amount is not supported in Real-time pricing. Please consider supporting behavior for negative amounts.

Our client has a requirement to track the tasks based on their status without a need to create time entries.

It would be useful to have functionality to allow a user (Project Resource) to set status directly on a task card.

Currently, we cannot customize "Utilization" table on "Project Operation" model driven app on make.powerapps.com .

This is expected behavior, but the error message below is displayed when we try to customize this, which is not user-friendly for some users.

Error: 

Failed to read a named property "UiTestGlobal" from "Window". Blocked a frame with origin "https://~~.crm.dynamics.com" from accessing a cross-origin frame.

It would be great if the displayed message is simpler to understand that this table is not customizable.

Also, it would be more user-friendly if we could customize the "Utilization" table on make.powerapps.com without any errors.

Regarding importing resource on Time Entry, if a task on a project record sets 0 on duration, the task is only displayed on that task start date and finish date is ignored.

Users might miss and cannot import the proper task due to this behavior when importing resource on Time Entry.

This behavior is currently by design, but this should relate to actual task finish date.

It would be much better if task duration precisely matches the display when importing resource on Time Entry.