How to Make a Custom Field Read-Only in Strategic Planning Workspace Planning Grid?

Brijmohan
Tera Contributor

Hi Community,

I have a requirement in ServiceNow Strategic Planning Workspace (Portfolio Planning → Planning tab).

We have a custom field named Project Number displayed as a column in the Planning grid. We want this field to be read-only for users, so they can view the value but should not be able to modify it through inline editing.

I have already tried configuring the field as read-only through the System Dictionary, but it is still editable in the Planning grid.

Could someone please suggest the recommended approach to achieve this requirement?

* Is there any OOTB configuration to make a specific column read-only in the Planning grid?
* Can this be achieved using ACLs, UI Policies, or any workspace-specific configuration?

Any guidance or a working approach would be greatly appreciated.

Thanks!

1 REPLY 1

kmohammed
Tera Guru

Hi Brijmohan,

 

You have hit the expected split between form behaviour and grid behaviour:

 

- The Planning tab grid is not a form. Its inline editing does not evaluate the dictionary "Read only" attribute or UI Policies — both of those are form concepts, which is why your dictionary change had no effect in the grid (and why a UI Policy won't fix it either).

- What the grid does honour is write access: a cell is only editable if the current user passes the field-level write ACL for that field. The grid column configuration itself (which columns show, order, grouping) has no per-column read-only toggle.

 

Recommended approach — field-level write ACL:

1. Find the write ACL(s) for the field on the underlying planning item table (System Security > Access Control (ACL)) — for a custom field, look at <table>.<your Project Number field> with operation = write. If none exists, the field is inheriting broader table-level write access, so create a field-level write ACL for it.

2. Restrict that write ACL so the users you want to protect against don't pass it — for a "nobody edits this manually" field (e.g. an auto-generated Project Number), require a role nobody holds outside the generating process, or an admin/integration-only role.

3. Leave the read ACL untouched, so the value still displays in the grid for everyone.

 

Result: in the Planning grid the column shows but the cell is no longer editable, and because this is ACL-based it is enforced server-side too — the same users also can't change the value through forms, lists or the REST API, which is usually exactly what you want for a system-generated number.

 

Two things to verify after changing it:

- Whatever populates Project Number (number generation, business rule, flow, or an integration user) must still pass the write ACL — test that path. Server-side code running as system is fine; an integration running as a named user needs that user to hold the role on the ACL.

- If you actually need the opposite split — read-only in the grid for most users but editable by a small group (say portfolio managers) — put only that group's role on the field write ACL; the grid will then be editable for them and read-only for everyone else.

 

So of your three candidates: ACLs — yes, that's the lever; UI Policies and workspace-specific column settings — no, neither can do it.

 

Hope that helps.