TM1 Forum

My users have an option to run a background process to get information from the system that feed TM1 for any intersection. This is done by selecting "Drill" in the options when the user right clicks on the mouse. When the process is finished getting the information, the user can view it by going back to the Server Explorer. But I have some questions.

1. Why does the result of the drill down is displayed in the server explorer screen window and not the cube window?
2. In order to get this information to Excel, you need to do a Select All, then Copy, which builds a temporary cube in the background. You then must paste the data into a empty excel spreadsheet. I thought there was a way that the drill down results can be sliced directly into Excel like cube data.

Any information on this will help. I think it is a great tool for my users to use to get supporting information on any TM1 cube intersection.

David Correia
XO Communications LLC

I can't make much sense of what you are describing. Possibly your system is very non-standard (but I can't imagine how as it would require special programming to override normal features) or possibly you have just not explained it very well. In this situation a step-by-step with screenshots to describe what you mean would certainly help.

1/ Normally when executing a drill-through from the cube viewer the drill results window should take focus when the drill is completed, you shouldn't need to go and find it. However if using Excel 2013/Office 365 there do seem to be some issues with new windows not taking focus and hiding behind the ones that called them, could that be it?

2/ Getting drill results to Excel. Well just execute the drill from Excel to start with. The drill feature works from any TM1 UI so if you right-click and drill from a DBRW cell in Excel then the drill result will be returned directly as a new worksheet

I assume the OP is referring to a drill through to a relational table as opposed to another cube. Which in fact doesn't build a "temporary cube" but just provides a flat table format... as to be expected when querying relational data. If thats the case change your drill process to instead have an ODBC datasource and actually do import the data into a temporary cube (even if its a 2d one to keep things simple) then use the viewreturnhandle function to open the new temp cube, then it will open up in a cube viewer and you can do whatever you want with it (slice dice etc.)