Failed TM1RPTROW to Load in TM1 Web: Having two TM1RPTROWS

[pikolikoli]

Hello Everyone,

I am using an If condition to choose between the Dimension displayed in a list.
My Cell formulas is like this :

Code: Select all

=IF( B1="Dim1",TM1RPTROW($A$1,ServerName&":Dim1","",,"DESCRIPTION",,A17,,0),TM1RPTROW($A$2,ServerName&":Dim2","",,"DESCRIPTION",,A18,,0))

with  $A$1=Server:CubeName:1 and $A$2=Server:CubeName:2

Also , I made sure every dimension it's proper formatting Section. But for TM1RPTDATARNG I made it point to the same line of my Table , since I want to always display the result in one Table.

The problem is when I choose dimension1 and Click rebuilt , it displays the correct values ?Same if I choose dim2. But When I load my Report to TM1 Web only One of them works ( the one I saved it with before uploading it). so If I choose dim1 and apload it with dim1 this one that will be working and vise versa.

I am suspecting that having TM1RPTDATARNG1 point to the same line is the cause of the problem.I would like to have both of them on the same line. If it is the reason of the problem is there anyway to make it work ? If it is not the cause of the problem , Can you help me please figurout a fix to make it work also in TM1 Web as it is working for me in perspective ?

Thank you in advance !

[gtonkin]

Your TM1RPTVIEWs are probably your issue. You said you are using "$A$1=Server:CubeName:1 and $A$2=Server:CubeName:2"

The first parameter is for the server:cube:name - the name component is what drives the named ranges.
When rebuilding and you have TM1RPTDATARNG1 it will probably use that. Referencing :2 may confuse the report rebuild.

I often change the name parameter to something like Review, Input etc. then go into the Name Manager and update the relevant named ranges there too. Once done, I rebuild and it generally works and is easier to reference, especially on PAfE where you have a nicely named range like 5973448

Long story short, try change the reference in A2 to Server:CubeName:1

Also make sure that in the TM1RPTView you do not have any TM1RPTTitles pointing to invalid references or dimensions that are now on the rows.

HTH.

[pikolikoli]

Your TM1RPTVIEWs are probably your issue. You said you are using "$A$1=Server:CubeName:1 and $A$2=Server:CubeName:2"

The first parameter is for the server:cube:name - the name component is what drives the named ranges.
When rebuilding and you have TM1RPTDATARNG1 it will probably use that. Referencing :2 may confuse the report rebuild.

I often change the name parameter to something like Review, Input etc. then go into the Name Manager and update the relevant named ranges there too. Once done, I rebuild and it generally works and is easier to reference, especially on PAfE where you have a nicely named range like 5973448

Long story short, try change the reference in A2 to Server:CubeName:1

Also make sure that in the TM1RPTView you do not have any TM1RPTTitles pointing to invalid references or dimensions that are now on the rows.

HTH.

Hello gtonkin,

Thank you for your replay and Help , I appreciate it.

I did as you suggested I changed the parameter to server:cube:Input1 and the other one server:cube:Input2 and named TM1RPTDATARNGInput1 and TM1RPTDATARNGInput2 . But I am still facing the same problem. (TM1RPTDATARNGInput1 and TM1RPTDATARNGInput2 both pointing to cell $20$20)

Also I made sure that if I select Dim1 in the list , its TM1RPTTitles will not contain Dim1. And when I select Dim2 its TM1RPTTitles will not contain Dim2 ..etc

In perspective it seem working. It displays the values in the same table whenever I choose a Dimension name in the List. But When I downloàad it to TM1 Web , it's not working it displays only the last dimension values that I saved it with.

Any Idea what would be causing this ?

Thank you Again

[gtonkin]

I was saying that they should both be pointing to the same named range i.e. TM1RPTDATARNGInput1
As soon as you have TM1RPTDATARNGInput1 and TM1RPTDATARNGInput2 it will probably not work.

Change the reference "server:cube:Input2" to "server:cube:Input1" - You can still try switch your dimensions etc. but don't fiddle with the named ranges that drive the report.

[pikolikoli]

I was saying that they should both be pointing to the same named range i.e. TM1RPTDATARNGInput1
As soon as you have TM1RPTDATARNGInput1 and TM1RPTDATARNGInput2 it will probably not work.

Change the reference "server:cube:Input2" to "server:cube:Input1" - You can still try switch your dimensions etc. but don't fiddle with the named ranges that drive the report.

Oh! My bad . I understand now. Thank you for the clarifications.

I did Remove the second one , I only Have one : TM1RPTDATARNGInput1.But still my report wont show the second dim if I switch it in the list in TM1 Web.


For my view I have it like this :

=TM1RPTVIEW(ServerName&":cubename:Input1", 1, TM1RPTTITLE(ServerName&":dim3",$M$35), IF( $A$2="Dim1", TM1RPTTITLE(ServerName&":Dim2",$B$39),TM1RPTTITLE(ServerName&":Dim1",$B$38) ))

Then I put TM1RPTDATARNGInput1 pointing to Ligne $50$50.

And for my TM1RPTROW I put this codition :

=IF( M42="Dim1",TM1RPTROW($B$9,ServerName&":Dim1","",,"EVDESCRIPTION",,A10,,0),TM1RPTROW($B$9,ServerName&":dIM2","",,"EVDESCRIPTION",,a11,,0))

Do you Have any idea what else should I change to make it work ?
Also sorry if I am asking noob questions I am still new to TM1.

Thank you in advance for your help.

[tomok]

Do you Have any idea what else should I change to make it work ?

I don't know the answer to your question but it's important to understand that while IBM tries to make active forms work the same way in Perspectives (aka an Excel sheet) as it does in TM1Web there are numerous instances where it doesn't. This is true especially when you "go off the reservation" (sorry, this is an American saying) and alter the way the active form underpinnings work like trying to make two active forms out of one by monkeying with the TM1RPTROW and TM1RPTVIEW formulas to insert IF logic or other special Excel formulas. I personally have never tried what you are attempting, mainly because I have been burned by the fickleness of TM1Web and don't want to spend time getting some jury-rigged scheme working in Perspectives only to find the minute I publish it and try it in TM1Web it breaks. If it was me I would abandon the idea of trying to share an active form area with two different cubes and look into putting the two TM1RPTDATARNG ranges on top of each other and dealing with a blank row in the event cube #2 is chosen instead of cube #1. You can make it invisible in this instance with conditional formatting.

[pikolikoli]

Do you Have any idea what else should I change to make it work ?

I don't know the answer to your question but it's important to understand that while IBM tries to make active forms work the same way in Perspectives (aka an Excel sheet) as it does in TM1Web there are numerous instances where it doesn't. This is true especially when you "go off the reservation" (sorry, this is an American saying) and alter the way the active form underpinnings work like trying to make two active forms out of one by monkeying with the TM1RPTROW and TM1RPTVIEW formulas to insert IF logic or other special Excel formulas. I personally have never tried what you are attempting, mainly because I have been burned by the fickleness of TM1Web and don't want to spend time getting some jury-rigged scheme working in Perspectives only to find the minute I publish it and try it in TM1Web it breaks. If it was me I would abandon the idea of trying to share an active form area with two different cubes and look into putting the two TM1RPTDATARNG ranges on top of each other and dealing with a blank row in the event cube #2 is chosen instead of cube #1. You can make it invisible in this instance with conditional formatting.

Thank you So much! This is worked for me ! I appreciate it. Just One last question if you don't mind : Do you know any good ressources That could help me to learn how to deal with Report creation and active forms in tm1. I would Love to Learn it in depth and know everything about it so I can feel more confortable with it. I appreciate your hep and Thank you agaéin

[gtonkin]

Glad Tomok could help you out.

There is a Guideline document still floating around out there but no longer on the IBM site by the look of it.
Try a search on : guidelines on working with active forms and ibm cognos tm1
You should get at least this result:
https://docplayer.net/34745669-Guidelin ... s-tm1.html

[pikolikoli]

Glad Tomok could help you out.

There is a Guideline document still floating around out there but no longer on the IBM site by the look of it.
Try a search on : guidelines on working with active forms and ibm cognos tm1
You should get at least this result:
https://docplayer.net/34745669-Guidelin ... s-tm1.html

Thank you So much gtonkin ! You cant imagine how much helpfull this is to me. I appreciate your help