51
There must be a data entity that works to import and migrate all the on account transactions for all projects.
The workaround solution provided was to use the forecast entities and import the project on account forecast and copy on account transaction from these forecast cannot be a real workaround when you will migrate hundreds or thousands of projects, that is a practical situation in the real life.
The workaround solution provided was to use the forecast entities and import the project on account forecast and copy on account transaction from these forecast cannot be a real workaround when you will migrate hundreds or thousands of projects, that is a practical situation in the real life.
STATUS DETAILS
Under Review
Comments
Thers should be entity for upload project milestones with in a project contract. While performing data opening activity there is limitation to upload multiples milestones within a project contract.
Category: Project Accounting
Here is what I used out of desperation: https://erconsult.eu/blog/electronic-reporting-in-data-migration/
Category: Project Accounting
Andy Choi (administrator)
Thank you for your feedback. This is a great suggestion! We will consider this in our roadmap.
Sincerely,
Andy Choi
PM, Microsoft