Hi Bjorn, that's not the issue, as i've encountered it again already and it doesn't make any difference.
What is even more concerning in this one is that the first DF in the procedure won't put ANYTHING into the cube, yet the second DF (which was a COPY of the first with an algorithm thrown in) will populate the cube. I've even gone all the way back to doing nothing in the DF other than putting a '1' into the cube... and it doesn't work...I get an empty cube as shown below.
That is the result of this extremely basic procedure with all the other actions disables.. and the save to disk applied..but if I enable 7 and 8..This is the working dataflow..The only difference between that DF and the original not working DF was the original didn't need the d block, it just used the c block (to apply to hours, as opposed to day)I now get data in the cube as is expected from the calculation.I've cleared the cube multiple times and it keeps getting populated with the second dataflow only.How on earth can that even be possible in BOARD?! If it can't flow a 1 to the cube, then how/why can a more complex multi-block algorithm possible populate it? I have tried everything, adding a new member to that entity to see if that's the issue, copying the one working dataflow and applying with the other members selected, absolutely nothing worked.But in trying all that now the 1 dataflow that WAS working doesn't work and now my cube stays empty - and all that I changed in the structure of anything was adding a new member to the Allowance Base entity.I can only think the DB is buggered...but the fact they get buggered so easily and frequently is very frustrating.
Hi Brendan,
Encountered yesterday an issue as well in a prod db. We were testing multiple scenarios, but a datareader which had to result a quantity=1, gave a quantity=2 for some cell combinations.
After wasting a full day in the web client trying to find workarounds, we opened the db in the windows version where we got the instantenous pop-up that a maximum item number went over the limit. After fixing this, the system behaved as normal again. Unfortunately that pop-up doesn't show up in the web client, so maybe it is something you can check.
Probably you will have done that already, but it could be something to take into account for anyone else reading this thread having an unexplicable reason why BOARD was providing inconsistent results and expected in the back of their head a similar pop-up in the datamodel in the web client.
Cheers,
Jonathan