Skip to main content
S
SaraA
December 13, 2024
Solved

Reusing Bi Blend attributes

  • December 13, 2024
  • 2 replies
  • 0 views

Hi All,

We currently have BiBlend set up to use all 20 attributes. We're considering reusing two attributes to load data from different columns (these attributes are currently used but are no longer needed). Our plan involves renaming these attributes in the Cube Settings and updating the data source.

Does anyone know if this is possible? Are there any restrictions or limitations on how attributes can be used or modified after the initial configuration?

Thanks in advance for your insights.

Best answer by rhankey

When naming/renaming register columns in the relational blend modules, all you are doing is changing a "display name".  The underlying columns in the SQL register table remain the same.  Same deal when enabling/disabling a column - all you are doing is cosmetically enabling/disabling whether the column is to be displayed, but the underlying column is always present in the SQL register table.

Code that reads or updates the register will be referencing the underlying SQL register table column names.  So, renaming or enabling/disabling columns should normally have no effect on the underlying SQL table.

Depending on how your relational blend solution was built out, there is a chance there is some code that was written to reference fields by their display name rather than their underlying column name.  So, it's probably a question you should pose to whoever implemented your relational blend module, along with asking them what the potential implications could be with repurposing a register column.

2 replies

R
rhankeyAnswer
December 13, 2024

When naming/renaming register columns in the relational blend modules, all you are doing is changing a "display name".  The underlying columns in the SQL register table remain the same.  Same deal when enabling/disabling a column - all you are doing is cosmetically enabling/disabling whether the column is to be displayed, but the underlying column is always present in the SQL register table.

Code that reads or updates the register will be referencing the underlying SQL register table column names.  So, renaming or enabling/disabling columns should normally have no effect on the underlying SQL table.

Depending on how your relational blend solution was built out, there is a chance there is some code that was written to reference fields by their display name rather than their underlying column name.  So, it's probably a question you should pose to whoever implemented your relational blend module, along with asking them what the potential implications could be with repurposing a register column.

S
SaraAAuthor
December 16, 2024

Thank you for the detailed explanation. This is exactly what I wanted to understand.

Terms & ConditionsAccessibility statement