Hi Good Data team, How can i change the name of attributes present here in the visualisation page. The screenshot mentioned the left side bar where all attributes are listing. I want to change the name here not in the visualisation without changing column name in the database.

Hello Haseeb, Are you looking to just change how they are displayed in the attribute selector? I'm afraid that is not possible without changing your LDM. However, you can certainly change how the attributes are displayed in reporting using labels.

I want to rename or alias attributes in the attribute selector. How can i do it in the LDM? could not find any such instruction here. Can you please explain?

It is not possible to change how they are displayed in the attribute selector unless you change their actual name in the LDM.

Hi Haseeb, to change the visual title of an attribute or fact in the model, you can simply double-click it in the model Edit mode and type in the new name. You can also open the dataset details and then in the “Fields” tab click the name and write new name there. However this change will no t only change how you see the attribute in the left sidebar, but also name of the columns (or data rows) in the existing visualizations unless you changed their name explicitly. Default name in visualizations is the current title, but you can override it in each visualization. You do not need to change the name in your database or anything in your metrics and elsewhere since there are three separate things of each object; • visual title (how it appears in the list) • identifier (how it is referenced in other objects) • mapping to database (which table and column it refers to)

Thanks @Joseph Heun @Michal Hauzírek for this update.

If you mean show some data model parts in the master workspace but hide them in child workspace, that is currently not possible unfortunately. You might try to emulate this by having the parent WITHOUT these columns (therefore the child workspaces without these as well) and then in some of the child workspaces modify the data model by adding new datasets and including these additional columns. However currently this only works by adding new dataset via API, not modifying the existing one or in the UI. Some customers use this approach to add “custom fields” to their child workspaces by connecting “core” dataset (from the parent workspace) to the “extra” dataset and connect them via M:N (double sided) arrow to allow filtering “core” by “extra” fields.

For example, i have some sensitive fields in the database which i do not want to expose to child workspaces. Like passwords or api keys. I want them to be available only for parent workspace but not to child workspaces.