Custom fields for objects | Voters

Custom fields for objects

Tim Gaweco

A way to add custom fields to an object that are searchable across the landscape, both in diagram and also in model objects list.

November 7, 2024

Oliver Windle

Merged in a post:

Add API resource ID's to model objects and resources in IcePanel.

Tim Gaweco

Add resource ID's to model objects, diagrams, object properties, tags, flows, drafts, versions etc.

November 15, 2025

Ángel Moreno | El Corte Inglés

In addition to what was said by Fausto Oliveira, I would add the ability to define types of fields (text, numeric, drop-down list, checbox, radiobuttons) governed, given that in our case we want to follow a Design-First methodology, and use IcePanel as a metadata repository to launch the industrialization of systems.

Tim Gaweco

Merged in a post:

Support for custom metadata

Fausto Oliveira

All objects, including connections, should have a metadata section where editors could input any form of structured data. 
I believe a large text box with YAML syntax highlighting and validation would be a good solution for this. It will also simplify the implementation on your side (no need to create and manage fields or tables).
This information should be searchable and also returned in API calls.
It can be used for many purposes, but my main interest is using it for integrating with other systems where I want to save, among other data, external reference ids.

January 17, 2025

Fausto Oliveira

Consider https://feedback.icepanel.io/feature-requests/p/support-for-custom-metadata instead

Fausto Oliveira

I tried using the "Description" of the object to add YAML front matter input between --- but the UI changes it to a ## section when I get out of the markdown edit view. It works without the --- separator, but this metadata should really have a dedicated place for it.