TM1 Forum

I'm having problems with a view expand that I published. This is a brand new cube that I made for one of my departments. Instead of displaying the data intersections, it displays "ERROR.BadMember". I have seen this before, but I can't remember what I did to address it. I thought it might be an issue with security, so I checked security for my test client, and they have read access to all of the necessary dims. The way I have the sheet set up, there are no title dims. As an alternative, I moved some of the row dims up as title dims, to see if that would solve my problem, but when I select a valid data point, there is no data displayed at all. Any fellow forum members with some suggestions as to what I can try next? Thank you for your thoughts on this.

I'm having problems with a view expand that I published. This is a brand new cube that I made for one of my departments. Instead of displaying the data intersections, it displays "ERROR.BadMember". I have seen this before, but I can't remember what I did to address it. I thought it might be an issue with security, so I checked security for my test client, and they have read access to all of the necessary dims. The way I have the sheet set up, there are no title dims. As an alternative, I moved some of the row dims up as title dims, to see if that would solve my problem, but when I select a valid data point, there is no data displayed at all. Any fellow forum members with some suggestions as to what I can try next? Thank you for your thoughts on this.

Hi there,

That error message is the equivalent of a KEY_ERR in the TM1 Excel client - the difference is that it (if you expand your column width) will tell you which element it thinks is the problem. These formulas might look OK when you've got it set up in Excel, but when the expansion runs in the web (dynamically pasting in the element names and repeating the rows based on the specified view) you could run into problems if your view was set up in a different dimension order than your spreadsheet is expecting, for example if Fund and Department was in the reverse order in the view by mistake.

Feel free to send a private message if you're still having problems.

Regards,
Mike

MIke-

I found the problem- when I had set up the dim names in the TI process, I accidentally used another dim name that wasn't supposed to be part of the cube, so the data intersections were going to be off. Thanks for your help!