Source: MC1492955 – Microsoft Planner: Introducing Local Custom Fields
Microsoft · Microsoft 365 Message Center · 9 October 2026
Found via mc.merill.net, the community archive of the Message Center
Why it matters
Custom fields are where project managers put what the tool does not have: a contract code, a client reference, a cost centre. Ten fields per plan, write access only with a Premium licence, and a deleted field is gone for good, so agree the conventions before the first field is created. One more thing to remember when a plan leaves the organisation: those fields travel with it, and they often hold the data you least want outside.
— Rosario Rizzo
Related
- The columns you’re missing already exist: the custom Text and Number fields Microsoft Project already has, and how to use them
- GanttShield: for Microsoft Project files: anonymise resources and tasks, clear notes and financial data, and send a clean copy
Rosario Rizzo’s NewsRadar: curated news on reliable schedules, the Microsoft Project ecosystem and practical AI, each with a comment on why it matters to people who plan. How we choose the news