(v24) Fields Usage

Fields Usage

This applies to: Visual Data Discovery

Symphony doesn't allow you to remove a field from a source definition if any objects rely on this field. For example, if your native field field_1 is used in a derived field expression such as year_to_time(field_1), you can't remove it from the source.

The table below is a list of objects where a field can be used.

Symphony Object Type Referencing the Field	Can't Delete from Source Configuration	Can Delete from Source Configuration
derived field	If used in derived fields.
custom metric	If used in custom metrics.
global settings > time controls	If used by global defaults, such as time controls.
global settings	If used by global defaults, such as time controls or global filters.
row security	If used in row security.
column security		If used in column security.
visual	If used by a visual.
key set	If a key set exists for the data source.
filter set	If a filter set exists for the data source.
row level filters (dashboards and visuals)	If used in a row level filter.
field link (cross-source link)	If used in a cross-source link as part of dashboard interactions.
same source link		If the same source link is in a publisher or subscriber link.
actions	If used in an action.
partition configuration	If used in a partition configuration.
join configuration	If used in a join configuration.

Note: If you try to delete a visual, filter snippet, dashboard, dashboard link, source, or source field, Symphony displays an error message naming any objects dependent on the item you’re trying to delete. You can delete the item after you’ve removed the association from the dependent object. See Fields Usage.