Hi,
I have an issue open with IBM in this space at the moment. (
TS009273622)I have found that any DBRA in any sheet will fail if there is a dynamic report open in any workbook that is failing or corrupted in some way. In my case I found that a user had been duplicating dynamic reports and then sliced a new DR into the same sheet creating a confused state and repeated sets of named ranges.
The TM1RptRow was formula was stuck in a pending state.
So I suggest you check all the workbooks that are open when the DBRA is failing and look for any DR that are failing wth Pafe errors (rather than Excel errors) and generally have a good clean up.
It seems as though the calculation refresh is being blocked somehow when the recalc of the corrupted DR fails.
HTH helps in tracking your issue
------------------------------
Steven Rowe - Technical Director - InfoCat
------------------------------
Original Message:
Sent: Fri May 06, 2022 08:40 AM
From: Sylwester Przybyla
Subject: DBRA function shows #value
Hi,
I encountered strange behaviour by the DBRA formula:
I use the TM1RPTROW function to import some Data into Excel. This works fine:

I then want to add some attributes through the DBRA function:
This works fine for the first row:

All other rows show the #VALUE error. The strange thing is: When i click into the formula bar and press enter the correct data is retrieved:


I can do this with other cells as well. If I press F9 to update everything all rows except the first show the #VALUE error again.
What is happening here?
------------------------------
Sylwester Przybyla
------------------------------
#PlanningAnalyticswithWatson