Dynamics 365 Project Operations

Working with item requirements is not allowed if multiple funding sources are setup in the project contract that is attached to the project.

It would be very helpfull if a design change was made which allowed working with item requirements and/or project sales orders in conjunction with a project contract with multiple funding sources.

A recent update based on KB3178570 made it impossible to change the project contract after project transactions were made. This was done to prevent a problem in a specific scenario. However, this also caused a regression in functionality.

All information from the project contract is stored in the project transactions, including the funding source. To that end changing the project contract on a running project should be possible. This allows users to change the customer (and other commercial details) of a running project for all new transactions. In the meanwhile the existing transactions can be invoiced based on the old project contract.

This functionality is even more needed since a funding source cannot be change while project transactions exist (which is good) and working with multiple funding sources is not allowed when working with item requirement and/or project salesorders.

The word 'Estimates' have always been confusing for clients when is introduced to them first time. In addition a lot of clients use 'estimate' to actually mean the 'quotation'. 

Now that the fasttab which holds the estimate have been renamed to 'Revenue recognition' it will be appropriate to start extending the renaming of the underlying objects as well. 

• On the MANAGE tab, the 'Estimates' link can be renamed to 'Recognise revenue'
• Once clicked and the 'Estimates' form itself is open, that 'Estimate' form can also be renamed to 'Revenue recognition'. 

Then maybe we can explore making the following changes as well:

• Estimate date > Revenue recognition date
• Estimate status > Revenue recognition status
• Estimate project > Revenue recognition project

Mobile App for Microsoft Dynamics 365FO does not allow logging of mileage. This is critical for many users.

The on-account transactions form holds lines for the different on-account transactions (Milestones, Deductions, Prepayment Journal lines, Beginning balances) depending on the project type. They can be created either via Billing rules or manually. 

• Client may use it in different ways, and sometimes where this is being used to drive invoicing that has been based off quotation lines, certain clients may want to see the individual lines broken down into the elements of build-up as it was in the quote. This result in potentially having to create multiple lines on the on-account form.  
• Also in a dense project hierarchy with on-account lines at different sub-project highlighting it at the top of the hierarchy can present you with quite a large number of lines. 

Required function

• Users require a TOTAL field, which is a read-only summary on this form to show a total of the lines. This easily allows the on-account lines to be compared to either the forecast/budget/quotation lines that have been created.

• This can be implemented by choosing to provide a single TOTAL which considers all the different types of the on-account lines or a box each for each type of on-account and a TOTAL that represents the sum of the individual total. 

• The TOTAL box should be able to reflect the correct totals in a mixed hierarchy of project types and the different levels within the hierarchy (ie be able to reflect the sums of all on-account lines from child projects within the hierarchy).

This will make a massive difference and improve efficiency of using this form. 

System should have line property default also in WBS task line. When employee enter activity in timesheet line, system give category By default from activity. Project manager should have possibility to assign also line property to wbs task line and default value should come to timesheet line after activity selected

Hi, there should be a parameter to enable the Project quotation review workflow process. Currently you can only process ('Send') a quotation if the status is Approved - and therefore if our business doesn't need to approve project quotations, we have to setup a workflow which automatically approves all quotations - and the user has to submit the quotation for approval and wait for the workflow jobs to process the quotation.

For purchase orders, there's a parameter which enables or disables the purchase order approval workflow, and the same should be available for project quotations.

Thanks

Tim Schofield

When Project Admins enter the Project Forecast manually, there is no total on the forecast entry window for data validation.