TM1 Forum

Hi all,
Long time lurker, minimal poster (but I do try and read it all!).

Short Version:
Has anyone successfully used a DBR(W) formula to provide the link file for an action button to support dynamic navigation through report packs?

Long Version:
We use (almost) duplicate application folders to give us the ability to control which version of a report pack a user sees. This is more about showing changes to a select group first before rolling it out more widely so we want to switch things easily and quickly. While the reports are almost identical they all have cell values that drive navigation through the report pack (forward / back etc). These cell values need to be updated when we move the report from one folder to another, which is currently a manual process. We could automate it using some VBA to step through the files in the background (other than the landing pages, all reports are uploaded to the server as references so we don't need to re upload).

This is all working for us, in Perspectives and TM1 Web.

To improve things we wanted to store the navigation values in a cube so that we could change them without having to edit the spreadsheets. We'd store the version a user was supposed to see in one cube. We'd store the values for the action buttons in another cube. Then in the spreadsheet we'd use the user version with the navigation cube value to drive the cell the action button was linked to.

This works in Perspectives but it's not working in TM1 Web. Have others made this type of thing work (and we're missing something) or is this just not possible? We've played around with the settings on the buttons and the way the link formula is constructed but the button just does nothing on TM1 Web.

And, I'd be really interested in whether there another approach that is better?

Hi,

I have used DBRW's as references to reports in Action buttons.

Can you provide exactly what values you are holding in the cubes the DBRW's are referncing and
how exactly you are referencing the DBRW's in the action button?

regards,

Mark

Maybe you can use Excel Function
https://support.office.com/en-us/articl ... e9b76f577f

#Syntax
Hyperlink(link，friendly_name)

#Example
Excel Cell:$A$1
Name:pFile
=DBRW(...)


Excel Cell: $A$2
Name:pServer
=DBRW(...)


Excel Cell: $A$3
Name:plink
="TM1:// "& pServer & "/blob/PUBLIC/.\}Externals\ " & pFile


Excel Cell: $A$4
=Hyperlink( plink，pFile)


And then you can click the Cell $A$4 to link other Perspective.




In addition, if you want to link cubeview you need use tm1webapi to replace Excel Cell $A$3
https://github.com/wokeketm1/Rebellious ... Webapi.txt

Thanks both - sorted.

We had been using a Cell("filename") function on the original model to work out which set of reports was currently in use (by extracting the sub-part that said it was in the "draft" or "final" report folder.

We had (belatedly) spotted that the "filename" parameter wasn't supported in Web and had removed the offending bit of code from the model. However, turns out we'd missed a bit of it and that was still being referenced - hence it was working in Excel and not in Web. Once we switched our thinking to use an attribute we have no problems with using DBRW to drive action button navigation.

The moral of the story is wait until Monday morning when something isn't working on a Friday evening - all becomes clearer after a break!