Basic Question about BI Viewer and Cube View MD data source Column Expression
I have a Cube View with three Account dimension columns - Net_Rev, Std_Cost, and a CVC calculated division column to calculate Std_Margin (Std_Cost/Net_Rev). Rows are a UD dimension representing the Product. In my Dashboard, I have a Cube View MD Data Adapter using this Cube View as the data. When I add a BI Viewer Pivot Grid, I want to display the same three columns - Net_Rev, Std_Cost, and the calculated column. I see CalcScript in the Pivot Grid's Data Source dimensions. How do I use it in the Pivot Grid to display the calculation that the Cube View was doing for that third column? I thought I might reference it in the Value filter along with the two Accounts, but it doesn't appear as a column in the Pivot Grid.
Creating a Conditional Statement within a Cube View
Need assistance building this logic in for two conditional statements to return a value. The logic reads if one row is greater than 0.20 and another row is greater than 0.20, then 0 is the cell value. If not, then 1 is the cell value. Please let me know if I can provide any additional details.
Carriage Return in Annotation data on Cube View
Hi All Does anyone know how to add a carriage return in Annotation text (if it's possible)? We have a Cube View with an annotation member that displays data. Currently the annotation text can take up most of the screen on some rows andit would be really useful to be able to enter a carriage return. I have tried Environment.NewLine, vbCrLf, \r\n, <br>
Version 8 formatting issue with Books/Cube Views produced in Excel?
Just checking to see if anyone else has been experiencing the following issue with Version 8. We are currently testing the upgrade from 7.x to version 8 and have run into a huge formatting issue with our books that are produced to Excel and sent out to management via postal service. The source cube views for a batch use the same column template. We have Excel column width formatting set up for each of the columns (but consistently on each column). When the cube views are run and exported to Excel, the column width is not being recognized in most of the columns. I have tried direct formatting, I have tried with a literal parameter and getting the same results no matter what. I don't see where I can attach the workbook itself but am attaching a screen capture sample . In this case text wrap is set to False and column widths are set to 100. Note the results. Oddly, in like the first book, some of the sheets ARE recognizing the column width. I'm just wondering if anyone has experienced this and has found a workaround or determined why this is happening.
cube view formula
Requesting assistance with a formula needed in a cubeview row. Im looking to add a formula to my CF forecast column, so the formula in the row would be: ((A#AccountsReceivable:T#2024M12:S#Actual:V#MTD - A#AccountsReceivable:T#2025M1:S#Actual:V#MTD)) +((A#AccountsReceivable:T#2025M1:S#Actual:V#MTD - A#AccountsReceivable:T#2025M2:S#Actual:V#MTD)) + ((A#AccountsReceivable:T#2024M2:S#Actual:V#MTD - A#AccountsReceivable:T#2025M3:S#Forecast:V#MTD))CubeView Parameters not Passing Correctly into a Business Rule though a Dashboard
Hello, my team and I have encountered the following unexpected behavior: District Loan Detail Dashboard On the initial display of this screen when we click "Run Drill-down" button, the 2 parameters from the Cube View do not get passed into the Business Rule correctly. As shown below in the error message: It passed in GRP_16 which was from the previous "Run Drill-down" process, instead of the selected row's value of GRP_26 (UD7: "26 - Principal", Flow: "EndBalLoad"). So on initial display, clicking on the first row, which is already selected, does nothing and passes the incorrect (previous) values from the cube view. I have to click on a different row and then back to the first row to get the correct parameter values passed to the Business Rule. If only one row is in the cube view I will never be able to return the correct results because it is passing the incorrect value. This issue has been present ever since we upgraded to version 7.3.3 from version 6.4.0. We appreciate your help, Cruz Vega