Forum Discussion
Microsoft Project Service Core Jan 2026 Update locked Plans table
We recently noted the Microsoft Project Service Core was updated to 1.0.161.1772:
This update has locked our Plans table, no changes are allowed to the forms and creating new columns is greyed out:
We cannot make use of Planner in our model driven app (Planner Premium, non-default environment). After a new Plan is created, the user receives this message when opening the Plan:
Two days ago we were in this version 1.0.160.2874):
and everything was working as expected.
Any guidance would be much appreciated as we are not sure if this is a permanent lock or once the update cycle is completed we will be able to go back to edit Plan forms and columns.
Thank you in advance
Hi Bridgeburn
According to our ticket with Microsoft:
A bug has been identified in Project Operations (PO) version UR62 — 4.161.0.1688 and PS Core version 1.0.161.1722. Microsoft has acknowledged this bug.
The Microsoft support team clarified that:
- Microsoft can run a backend script to address the issue, and this may take up to 48 hours to take effect.
- However, the script is only required if you are already on the fixed version and the issue persists, which matches your scenario.
Fixed version:
The first released version after the affected build (4.161.0.1688) is Dataverse 4.162.0.962 (January 2026), which is the fixed version that resolves the issue. https://learn.microsoft.com/en-us/dynamics365/project-operations/whats-new/whats-new-home-page
In our ticket we successfully got unlocked the msdyn_project table when the Microsoft support engineer run the script in two of our affected environments.
Hope it helps
14 Replies
Anyone gotten a confirm from Microsoft that this is a bug they are working on?
Have anyone gotten an official response from Microsoft if this is treated as a bug?
Hi Bridgeburn
According to our ticket with Microsoft:
A bug has been identified in Project Operations (PO) version UR62 — 4.161.0.1688 and PS Core version 1.0.161.1722. Microsoft has acknowledged this bug.
The Microsoft support team clarified that:
- Microsoft can run a backend script to address the issue, and this may take up to 48 hours to take effect.
- However, the script is only required if you are already on the fixed version and the issue persists, which matches your scenario.
Fixed version:
The first released version after the affected build (4.161.0.1688) is Dataverse 4.162.0.962 (January 2026), which is the fixed version that resolves the issue. https://learn.microsoft.com/en-us/dynamics365/project-operations/whats-new/whats-new-home-page
In our ticket we successfully got unlocked the msdyn_project table when the Microsoft support engineer run the script in two of our affected environments.
Hope it helps
Another update in our US Early Release environment (1.0.163.579):
This version continues blocking the msdyn_project table to create columns and modify forms. No changes.
I had an email from Howard Crow regarding this issue, all he said was "The change takes time to roll out FWIW"
There was no indication on timeframes for a fix or any acknowledgement his team understand the impacts this is having on enterprise customers.Pretty disappointing, but not unexpected I guess.
We would like to add our voice to emphasize the critical urgency of this issue. We are in the midst of a large‑scale organizational deployment and must continuously adjust the solution as part of our rollout. Losing the ability to modify the Plan table is effectively bringing our implementation to a standstill and preventing us from meeting our deliverables.
This situation requires immediate attention, and the change urgently needs to be reverted.
Our US Early Release Cycle environment has been updated to version 1.0.162.956:
Unfortunately, this update does not resolve the issue with the Plan table (msdyn_project), which remains locked for customization. 👎
I sure hope Microsoft will eventually publish some article acknowledging this bug and the impact it has had on customers and partners. Meanwhile, I wrote my thoughts about this incident here: The kill switch in Microsoft Planner
We are experiencing the same issue. We customized the Planner Accelerator Model-Driven application and added custom fields to the project table. This is a major problem
We have also noticed this across multiple customer environments, and it is causing major issues. This change needs to be reverted immediately. We can't have the ability to create custom fields and views removed overnight from the system.
AlexanderLahuerta could you please comment on this. The 22 january 2026 is really blocking any development on the Project-app related to Planner Premium.
