-
Project item journals are unable to post in next open ledger period with “Automatically set accounting date to open ledger period” parameter on
Suggested by Alfie Ta (Tek Experts) – Needs Votes – 0 Comments
With the “Automatically set accounting date to open ledger period” parameter on in Project management and accounting module, it should allow user to post journals (Hour, Item, Expense, and Fee) in unopened period. However, it works for Hour, Expense and Fee journals, and blocked only Item journals.
-> This issue causes lot of additional work to the users to change the transaction dates for every work order line and process the work order once again through Field service integration
-
Intercompany tax in Expense Management for non-US regions
Suggested by Ivy Yu – Needs Votes – 0 Comments
In Expense Management module for Australia legal entity, intercompany GST is not posted to the correct legal entity. The issue happens when the expense is directly charged to the destination legal entity, without project linked to the record.
- The expected results: when General ledger parameter Legal entity for intercompany tax posting is set to Source (Destination option is for the US tax as shown in the description), the GST portion in subledger journal and voucher transaction should be posted to Source legal entity. Also, the Posted GST in Tax module should be recorded in Source company as well.
- The current posting pattern is incorrect: GST portion in subledger journal and voucher transaction is posted to Destination legal entity, however, the Posted GST in Tax module is recorded in Source legal entity.
Fixing the intercompany tax will make this module stand out from competitors and enhance its competitive advantages. I would appreciate it if this could be put on the roadmap.
-
Dynamics 365 Project service order per planned priority tasks scheduled resources expenses preferences
Suggested by Francisco Orozco – Needs Votes – 0 Comments
Wish there is an option to easily schedule and priority tasks expense resources process transaction planned tasks as per priority or priority role origin preferences, for purpose to maintain user role, planned and expenses priority tasks, for purpose to potentially justify main project goal (s) or feedbacks.
-
The On-account transactions form doesn’t have the credit note transactions
Suggested by Sreedhar Burgula – Needs Votes – 0 Comments
The On-account transactions form doesn’t have the credit note transactions, this can be tracked from the Invoice journals.
There is currently no overview of posted credit note transactions. The only way to check if a credit note was sent is via the invoice journals. However, when the number of invoices becomes large enough, finding a credit note becomes challenging. Furthermore, in the on-account transactions form, the original transaction remains without any matching credit note transactions. This can be confusing for the end users.
-
Add ability to copy Expense records like one is able to copy Time Entry records.
Suggested by Kunihiko Hayakawa – Needs Votes – 0 Comments
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.
-
Ledger to Expense Management reconciliation for Cash Advances
Suggested by Jessica Wells – Needs Votes – 0 Comments
Similar to the way we have a ledger to AP reconciliation report, we need the ability to reconcile against the cash advance balances within the expense management module.
-
Change Schedule mode on task
Suggested by Hans-Peter Dinser – Needs Votes – 1 Comments
It should be possible to change the pre selected Schedule Mode from the Project Header on the task. This makes it easier to plan task deppending on the different requirment of work.
Example. If the shedule mode on the project header is "Duration" and I have a task where I want the system to change the duration based on the effort, I want to change this single task to schedule mode Effort.
I think this functionality was available in Project Service Automation
-
Default Auto Scheduling Off
Suggested by Laura Mikulski – Needs Votes – 0 Comments
Allowing a setting where Auto Scheduling in WBS is defaulted to off.
-
Configurable default unit for Task duration in Project form Task tab
Suggested by Takamitsu Endo – Needs Votes – 0 Comments
Current behavior:
Default unit for Task duration is not configurable. If we put just "1" in duration column, it will automatically be "1 day"
Ideal behavior:
Default unit for Task duration is configurable (with user setting or global setting). We can change a default duration so we don't need to type "h" or "hour" in duration column every time.
Background/problem:
Depending on the usage and business, the most frequently used units of task length vary. Some people use "day" most, others may use "hour" or "week". For those who almost always use "hour", entering "hour" (or even "h") in task duration every time can be a hassle.
In addition to that, in Japanese environment, "hour" or "h" doesn't work. User should enter "時間" (means "hour" in Japanese) every time. Actually this requires many key types.
To do this in Japanese environment, basically user needs to type at least
- ` (to change input mode from English to Japanese)
- j
- i
- k
- a
- n
- [Space] (to transform "jikan" to "時間")
- [Enter] (to fix the input)
Doing this every time is quite a burden especially there're many tasks.
Please consider to make a default unit for Task duration configurable.
-
Allow linking of WBS to GitHub Issues
Suggested by Henry Staples – Needs Votes – 2 Comments
As a software development firm, our engineering teams track all their work items in GitHub Issues (and GitHub Project == Agile Project Iteration). We have an overarching WBS for the company. Within our engineering, we'd like to have a project iteration schedule in Dynamics ProjOps with sub-items that link to the applicable GitHub Issues. ***Then*** we would like to have eng team enter their hours for the GitHub Issue item and that roll-up into the WBS work package.
So, our WBS would look like this ==>
Company
Engineering
Project 1 Iteration 1
Work Package 1
GitHub Issue 1 (eng team tracks hours here)
GitHub Issue 2
GitHub Issue 3
GitHub Issue 4
Work Package 2
GitHub Issue 5
GitHub Issue 6
If you can accomplish this, then we could do away with some homegrown tracking methods and replace fully with GitHub and Dynamics ProjOps. Please contact me if you have any questions.
