attributes in data tab

[Moh]

hi sir why attributes updated in data tab instead metadata. any particular reason please explain

[bgregs]

In simplistic terms, metadata is the "mapping/webbing" behind the scenes where objects and data structures are linked together. When you update an element by adding it to a dimension in the metadata tab, you are creating this linking of element to dimension.

The data tab stores individual values in a data structure (in this case a cube). When you add an attribute to an element, you are literally storing data in the attributes cube for that dimension. You are not necessarily creating a "linking" to anything behind the scenes per say, but more so storing data in a cube about a certain element.

Hopefully that was clear. I tried to keep it high level, but obviously there is more than just that occurring behind the scenes.

[tomok]

In database terms metadata represents the structure in the tables; columns, indexes, etc. Data is the rows in the table. Since attribute values are data it is be done in the Data tab. If you were adding an attribute to a dimension, meaning the structure, and not actually adding the values for the attribute, than would be done in the metadata tab.

[jim wood]

Something to consider is commitment... Now then fellas don't all run away!!!

I mean when TM1 commits changes. Unless you're using the add direct formula the elements aren't committed to the dimension until once the meta tab has been completed. As others have others have stated attributes are simply data held in a control cube, so when TI was first created the attribute write was put in to the data tab as the element needs to exist before any data can be written to it, hence the write comes after the creation commit,

Jim.

[Moh]

thank you