Dynamics 365 Project Operations

Description:

The system requires a WBS to be published before attachments can be added to WBS ID lines. This limitation restricts users from attaching important project-related documents during the planning and preparation phase when the WBS is still in draft mode.

Proposed Enhancement:

Introduce the ability to attach documents to WBS ID lines while the WBS is still in draft mode, eliminating the need for publication first.

Benefits of This Enhancement:

• Improved Workflow Efficiency: Users can upload, reference, and review essential documents without needing to finalize and publish the WBS.
• Enhanced Consistency: Aligns with other areas of the system that allow attachments to be added to records in draft stages.
• Better Planning Flexibility: Supports project teams by allowing full utilization of the WBS for early-stage tracking and collaboration.

The D365 system allows us for posting negative journals because it only checks for overruns, not underruns. This means the system permits transactions that go below the budget and journal entries give users full control over postings, allowing negative amounts to be posted, which can lead to budget underruns.

While the system can handle budget overruns by disallowing or warning users, there is no similar control for budget underruns.

My example below will show what we are thinking.

1. I have an investment project budget with approved budget of 1000
2. Then I posted a PO of 1000 using cost category map to capex project category. (GL gets hit and CIP gets hit)
3. Now someone goes in and post an expense journal using the same capex project category with -1000. ( the CIP is cleared)
4. However, on a budget nothing changes. (no effect with the negative posting)
5. Now, if the user tries to post further negative expense journal they still can. Further affecting the ledger with negative posting.

The design might not have impact on subledger but the ledger balance will not match with sub ledger because of this. 

In a real life situation it is like

1. I have 5 in my pocket
2. I bought something for 5
3. Now the budget is 0
4. Then I go and return 10
5. The system is allowing.

Logically, you should only be allowed to return 5. And the return value of 5 should correct the budget. 10 should never be allowed to post. Furthermore, if the 5 is already estimated to FA, then it should not be allowed to be reduced by any means.

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.

When a user adds a D365 environment to Microsoft Teams, specifically a Project. The user cannot start a task conversation across other Teams members that are invited to the channel.

We would like to see the inclusion of the "Task Conversation" button to a task in the D365 PO task, details tab form when integrated to Microsoft Teams.

Current behavior means that only Microsoft Project tasks have the "Task Conversation" button in Microsoft Teams.

Alternatively as Microsoft Project stores the D365 PO grid of tasks, provide a way where the project can be made accessible to non D365 users in Teams as it is simply sharing the underlying PS tasks anyway. The licencing guide states that a D365 Team Member has access to tasks but gets an error when viewing the task grid in D365 PO even when they have a PO Plan 5 licence.

After bug fix of 286310, we see the project financial dimension for sub project considers is its own project id when "Copy values to this dimension on each new project created" is enabled in financial dimension form.

However, it is good to have this as a parameter that allows customer to choose whether to inherit the project financial dimension from the parent project or not. 

Microsoft Reference - FinOps - 875531

Project Budget Revision difference between Front end View vs. Detailed view - table rec ID overlap issue

we have worked on the table records and noted below bug in the code, could you please help us to fix this bug. 

Generally the RecId and RevisionIds follow an incremental pattern which the query below (even you mentioned in repro doc) also assumes.

As validated from the customer data this assumption in below query is incorrect. The same we can reproduce by altering the RecIds in standard env.

while select RecId from budgetRevision

      join RecId from projBudget order by budgetRevision.RevisionId

        where projBudget.RecId == budgetRevision.ProjBudget

          && projBudget.RootProjId == projId

          && budgetRevision.RecId <= this.RecId

Now as of this incident, we can mitigate it by correcting the RecIds of Revisions to follow same order as RevisionIds and all other tables where it is referenced.

However as we have the correct data in Details View (by clicking on Edit for each revision), I think it's better to fix this query itself.

The current approval experience is not geared towards reviewing and approving time efficiently.

1. The Approval screen should allow approver to view weekly totals by date, resource and project.
2. It should have a similar grid view as time entry to allow for a better overview of submitted time
3. An Approver should not be able to change filters and view other approvals, which could give rise to compliance issues

Description:

There is no way to add a second attachment to expenses via the mobile expense report.

Create expense via mobile app. Notice that once a receipt is added, the only option is to view the receipt. There is no way to add a second page or attachment. Add a receipt via the mobile app and attempt to attach it to the existing expense: 

Notice the only option is to replace the existing receipt: 

Select No and nothing will happen. Select Yes and the new receipt will become the only receipt: 

Expected results: There should be an option to add multiple attachments when there are multiple pages to a receipt or other scenarios (as is available in the web app).  

Idea is to triggering IC invoices in D365 related to the creation of intercompany customer invoices in the case of stocked/production projects related to time recorded cross company.

Right now, this needs to be handled company by company in D365. For a shared service center, with the massive number of companies live in D365 (and still growing) this is very heavy workload.

When Expense report is rejected user not possible to remove a line but only adjust existing lines.

Only option to Recall the Expense Workflow lost Expense history and rejection reason.

Also not all users have rights to Recall Workflow.

Users should be able to adjust Expense report as draft when Rejected.