Dynamics 365 Project Operations

In Microsoft Dynamics Project Operations, when a custom attribute is added to the task grid, its default value is not automatically applied to new records. This issue occurs even though the default value is correctly configured in the attribute settings. Interestingly, the behavior appears to be linked to the visibility of the column: when the custom attribute column is added to the task grid, the default value is not populated; however, when the column is removed, the default value is applied as expected. This suggests a potential bug or limitation in how the task grid handles default values for custom fields.

Environment: Project Operations non-stock

Information: Microsoft time standard time zone is UTC - Universal coordinated time. When a transaction is made for actual transactions the transaction date uses the users specific time zones. The transaction date which is time zone independent shows the correct date.

Issue: When a user changes their local time zone from UTC, and their personalization to their local time zone, then the Document date/Accounting Date are one day off from the transaction date. This poses confusion and inconsistency.

Idea: Solution to make document date/accounting date consistent behavior with transaction date.

Business Value:

Improved decision-making, enhanced trust in the system, reduce risks

In forms, allow that in choice type fields, with the multi choice option active, the hidden values ​​do not appear in the selection list for the user, as happens with the same type of choice field without being multi value.