Hi,
Thanks for your replies.
the main need is to have the char1 values, and its attributes, at the query run time and not the values at loading time.
if I add char1 the cube, there will be a generation of SID when loading and I would have the values at loading time and this is not the requirement.
To give you an idea about the global need, the only items that do not change in the cube are the customer and the material (this is char2, a compounded characteristic that carries char1 as navigation attribute), and char2_nav1 is already managed as transitive attribute, the idea now is to have acces to nav1 attribute dynamically without making them also as navigational attributes of char2.
Hope i the idea is clear.
Thanks.