TM1 Forum

The workaround:

Change your DBRW's to DBR's - BUT you need to keep one column of DBRW's. Now the column that stays DBRW will still return only 0's, so you have to make it a dummy column and hide it, but it triggers the DBR's to calculate.

Don't you love TM1?

Heard from Support: This is a known issue that is fixed in 9.5.1 FP1 and 9.5.2 (both due out later this month). See notes below: Some Active Forms that work in v9.4 and v9.5.0 stop working in v9.5.1. Trying to recreate the Active Form from scratch in version 9.5.1 also does not work the Active Form ...

Interesting - the ctrl-shift-alt-F9 does the trick. Thanks for the tip. I do know that AF's are quirky, but we've rolled out some pretty elaborate AF-based models and we've always gotten them to do what we needed ("creativity" is key). Not getting numbers in the AF directly after slicing i...

I'm experiencing the same phenomenon as you describe here. There are no rules on the cube, there's no aliases turned on, I'm "slicing" a very basic Active Form and getting all zeros. I can get the values to show up by just performing an Excel Save, but refreshing/rebuilding the Active Form...

Have you had any further developments on carriage returns in TM1Web? We're experiencing the same issue and to echo robert's note, without the ability to break up the text, it does limit the usefulness.

Thanks,

Andrew

I ran into this a while back and IBM confirmed this is expected behavior. Any action you take that could impact the mdx results (such as a cellputn) will cause the mdx to re-evaluate. Just writing to an ASCII file wouldn't cause a re-evaluation I have found the same issue if I try to directly create...