I built cube with 2 dimensions with 2 string elements 'Column1' & 'Column2'. This code significantly increase process using and on our work model with huge cubes led to loosing control on Arch. Is it bug or feature?
I am very surprised that this rule compiles. I get a "syntax error ... logical expression" as a ['element'] reference is always numeric and @= expects a string on both sides. Can you confirm that this rule is exactly as you took it from the cube, that it saves without error and also what version you are using?
I built cube with 2 dimensions with 2 string elements 'Column1' & 'Column2'. This code significantly increase process using and on our work model with huge cubes led to loosing control on Arch. Is it bug or feature?
What do you mean by "loosing control"? How big is the view are trying to open? Do you realize that this rule is going populate every single value for Column2? If you are trying to open a view that shows the entire cube you may be overloading TM1. Suggest you trim down the size of the view.
Assuming the syntax is valid, a two dimensional cube with a rule like this is trivial. Unless you have several million elements in one of the dimensions this rule is not a big deal at all and should take milliseconds to save the rule and also to calculate when you open the view.
I think you may not be giving us the whole picture. Can you show the actual rule that you're using and the cube structure that you're using.
Martin
Please do not send technical questions via private message or email. Post them in the forum where you'll probably get a faster reply, and everyone can benefit from the answers. Jodi Ryan Family Lawyer