Genesis - Drill down > Open in New Tab
I am testing out drill functionalities in Genesis and found this "Open in New Tab" being grey out. I checked the cv in the page and am unable to find any config in this cv that relates to this. How do I make this option active for use? it will be really useful to see the drill results in another tab so that it can be view side by side with the original dashboard.Genesis - User action to refresh another cv basic
Hi, I am trying to create a genesis dashboard that will have a main cv (1105) which shows overview and then when user click on the cell, it will filter another cv (1106) (probably cv basic since it will have navlinks on most dimensions). In client dashboard, it requires the config of setting of user actions in 1105 cv component but I could not find this setting in content block CV Advanced. I can find it in CV adv embedded. I assume this is the correct content block to use. I managed to get this function to work when 1105 and 1106 are on different pages. This means the cv are both setup correctly with navigation links dynamically set up correct. But they cannot be in different pages in Genesis because that means user need to click on cell in 1105 in page 1 and then go to page 2 to see filter results in 1106. That is too much work for user. , Thus, I created a dashboard advanced layout and try to insert cv advanced embedded of 1105 in row 1 and then cv basic of 1106 in row 2. for user action in 1105, it is very difficult to select the right component to refresh. I chose the name that is closest to the genesis given name for the basic cv 1106. but this did not work. When I clicked on the cell in 1105 in row 1, nothing changes in 1106 that is in row 2. See below. What is wrong? The list of "component" in the dashboard selector is sooo long. I trial and error a few and some seem to be just a filter selection page in a content block created. Is there any documentation that will explain which one or type to choose? I checked the user documentation for cv advanced embedded and it does not mention much.
Genesis cannot start: "Value cannot be null."
Hi What to do when I get this error messages in Genesis: Unable to open dashboard 'OpenPlace_(Designer)'. Error processing DataSet 'GetWFSteps'. Error executing Workspace Assembly Service class 'Workspace.Gen.CubeViewCharts_x2x.MUAssemblyFactory'.Value cannot be null. (Parameter 'reader'). How to reset? The problem happens when working with Block: Cube View Charts. It will not read my cube view and give the following comment: Value cannot be null. An error messages that is difficult to work with, as it does not say where the problem is. But this second, as I cannot get into the genesis instance.Genesis when in client - Taskbar excel etc
Below is a screenshot of how the genesis dashboard look like when it is used inside the client. The report on the left is the source cv and report on the right is the drill down details when a cell is clicked on the left. You can see that there is no taskbar for excel download etc in the left report, even though I have set cv default header to be visible. Both the left and right reports, I am using cv advanced embedded, but the left one is the one with user action "refresh" with click. I used the source cv of the left report as content cv with comments in another page and there is taskbar for excel download. The only difference between the two of them is content block type and user action. I checked the user guide for cv with advanced embedded, there is nothing written that when user action is selected, the taskbar for excel download etc will be gone within client. How do I get the taskbar for excel etc to appear when using genesis within the client?
Dynamically changing a Cube view row to allow Input
I have a requirement to allow users to enter an Annual Plan and spread it across Plan Periods using the spread method they select. Spread Methods are Equal Spread, 4-4-5 Weekly Spread and Manual. When they select "Manual" the cube view should dynamically pick O#Forms as Origin member for Data Entry. I have the Account and Product in rows with member expansion (.Base). Is there a way to retrieve the Base Account and Product from Cube view dynamically and reference in an XFBR?My plan is to get the Spread method chosen for the Base Account and Product combination and Return the Origin as O# Forms for that row? Please share any other ideas if you may have implemented for the same requirement?
Spreadsheet via Browser dashboard (OnePlace)
Hello everyone, I am currently working on OneStream v9.2 and trying to set up Ad Hoc reporting in the Web version (OnePlace). Context: I created a Dashboard with a Spreadsheet component exposed in Web (under OnePlace Dashboard). The connection to existing, preconfigured Cube Views is working correctly. Issue: In the Browser version, I do not have access to Quick View / dynamic POV features like in the Spreadsheet WinApp (Excel Add-in). I cannot find the option to perform free-form Ad Hoc analysis (changing axes, selecting members dynamically, etc.). Question: Is this a standard limitation of the Web version (OnePlace) in v9.2? Is there a specific configuration that enables a Quick View–like behavior in Web? Thank you in advance for your feedback and experience.Cache dashboard results to improve performance when switching tab?
Hi folks: I am searching for suggestions to improve reporting performance in dashboards. We have a couple of simple, executive dashboards that consist of 5-10 tabs of cube views. These work great for managing a common set of reports for end users. Parameters are managed within the dashboard and persist when switching cube views (tabs); all that works great. However, users complain that it is slow to switch between cube views (tabs). It appears that each cube view is re-run when switching tabs rather than simply displaying the data that was previously refreshed. While most reports take <2 seconds to run, a few can take in the 8-15 second range which is deemed unacceptable. Are there any methods (formal or hacked together) for caching cube view results so that switching tabs simply displays already refreshed data rather than re-running the cube view? Thanks, -dbThe Dynamic Grid Dashboard Component
Are you frustrated by volume limitations and the inability to edit data in grid view? Do you find the SQL Table Editor restrictive because it only supports a single table? Are your items taking too long to load in these grids? Discover a smarter way to load data on dashboards and grids: the Dynamic Grid dashboard component. Traditionally, OneStream grids have been limited in customizations, flexibility, data retrieval and data manipulation. The Dynamic Grid changes that traditional pattern. It allows each of those items in a more robust and enhanced way. Also, the Dynamic Grid allows for multiple data sources from a single component (however out of scope for this article). The Dynamic Grid loads only the data you need—nothing more. Dynamic Grid delivers unmatched flexibility: you can customize your grid to fit your company’s exact requirements. Enjoy traditional column formatting from the SQL Table Editor, now enhanced with powerful row and specific cell formatting options. I could go on about how powerful this new dashboard component is—but you are here to learn how to set it up. Let us dive into an example of creating a Dynamic Grid. The Dynamic Grid relies on two out‑of‑the‑box functions: GetDynamicGridData and SaveDynamicGridData. GetDynamicGridData retrieves the data for display in the grid. SaveDynamicGridData persists changes made in the grid—whether you are adding, updating, or deleting rows. Together, these functions power efficient data retrieval and safe, transactional saves for the Dynamic Grid. GetDynamicGridData Example Code: The first line— If args.Component.Name.XFEqualsIgnoreCase("Grid7") Then —acts as a conditional check to segment multiple Dynamic Grids within the same assembly. In other words, it ensures that the logic applies only to the grid named Grid7. This name must exactly match the Dynamic Grid component name defined in your dashboard configuration. Immediately after the opening If condition, you will notice two key arguments: startRowIndex and pageSize. These variables define where the table should begin rendering and how many rows appear per page. Without them, the grid would attempt to render the entire data, which would create serious performance issues. Here is what you need to know about pageSize: pageSize is driven by the Rows Per Page property on the grid. By default, Rows Per Page is set to -1, which means the grid uses your security settings to determine row limits. If you specify any value other than -1, that value overrides the security setting. The maximum allowed page size is 3,000 rows per page. Setting these arguments correctly is critical for performance and user experience. The next few lines use standard OneStream and .NET objects to open a database connection and create a command—nothing unusual there. The real magic happens in the SQL query, which leverages the lesser known OFFSET and FETCH clauses for efficient paging. These functions allow you to return only the rows you need, rather than loading the entire dataset. Alternatively, you can implement paging by generating a RowNumber column and filtering with a WHERE clause, such as: “WHERE ((RowNumber >= {StartRowNumber}) AND (RowNumber <= {EndRowNumber}))” Both approaches achieve the same goal: controlled data retrieval for better performance. Note: When building a Dynamic Grid with SQL, always follow best practices for writing SQL queries. This ensures your solution is secure, efficient, and maintainable. Notice the StartRowNumber and EndRowNumber variables integers. These are driving the SQL parameters inside of the OffSet and Fetch section of the SQL query. Using parameters is essential for pagination because it ensures your query retrieves only the requested rows while preventing SQL injection. The next section of code handles data retrieval and paging metadata: First, a new DataTable is created and populated using the SQL query for the current page of records. Then, “Dim SQL As String” defines a COUNT query to determine the total number of rows in the underlying table. A second DataTable is used to execute this count query and retrieve the result. Finally, the line: “result.TotalNumRowsInOriginalDataTable = $"{dt(0)(0)}" assigns the total row count to the XFDataTable result object. This property is critical for paging—without it, the grid cannot calculate how many pages to display. In short: no total count, no paging. Once all the arguments are in place, the final step is to create the XFDynamicGridGetDataResult object. This constructor requires three key inputs: XFDataTable – The data table you populated earlier (e.g., the result variable). Column definitions – We will cover these in detail later in the article. DataAccessLevel – Determines how users interact with the grid data. You can choose from: .AllAccess – Full read/write access (most common for editable grids). .ReadOnly – Users can view but not modify data. .NoAccess – No data interaction allowed. For most scenarios involving data manipulation, .AllAccess is the recommended setting. Note: As of now, it’s on the roadmap for paging and the ability to ascend and descend columns. This functionality is not currently available as of the writing of this article. SaveDynamicGridData Example Code: In the previous section, we focused on rendering data. Now, let us shift to saving modified data, whether inserting, updating, or deleting rows. With the SQL Table Editor, save functionality is built in. However, the Dynamic Grid offers far greater flexibility, which means you will need to implement custom-saving logic. This approach gives you full control over: How data changes are processed Custom validation rules User messaging and error handling Custom saving functionality ensures your grid behaves exactly as your business requires. Let us break down the code for the SaveDynamicGridData Function step by step. In the save routine, you will see two argument objects sourced from args: Dim getDataArgs As DashboardDynamicGridGetDataArgs = args.GetDataArgs Retrieves context from the earlier GetDynamicGridData call (e.g., paging, filters, sort)—useful if your save logic needs to reference the current view. Dim saveDataArgs As DashboardDynamicGridGetDataArgs = args.SaveDataArgs Initializes the save payload: inserted, updated, and deleted rows, plus column metadata. Next, the code gathers what is editable: Dim editedDataRows As List(Of XFDataRow) = saveDataArgs.EditedDataRows Gets the list of rows that have been modified, inserted, or deleted. This is often the entire row set, but you can scope it to specific rows when only part of the data should be editable. Dim columns As List(Of XFDataColumn) = saveDataArgs.Columns Provides the columns list (names, types, formats) for the target table—critical for validation and parameter binding. You will also see a simple table name string (e.g., Dim tableName As String = "dbo.sample_data") to identify where the changes are saved, and a Boolean flag used later to control behavior (such as enabling/disabling validation or transactional commits). Finally, the code re-opens a database connection to perform the actual writes (insert, update, delete). This is done in the save path to keep read and write operations logically separated and to ensure that any transactional logic is scoped to the save operation. Now we are moving into the fun section of code. This opens with a Loop (For Each) of all our possible edited data. Then you see the Case Statement “editedDataRow.InsertUpdateOrDelete” This lets the application know that we want to apply the insert, update or delete functions to our available edited data rows variable. There is no easy part to the modified sections. Each of them takes their own separate lines of code that are functionally SQL Statements. As you can see from my previous screenshot, I have created three separate functions to dynamically run these queries. I will post these code snippets as an appendix to this blog. For the function of InsertDataRow, this is using the standard SL Insert statement. Now we get to the save loop. The routine starts with a For Each loop over the collection of edited rows. Inside the loop, a Select Case editedDataRow.InsertUpdateOrDelete directs the logic for each row, applying the appropriate insert, update, or delete operation. There is no shortcut here, each operation requires its own parameterized SQL command and validation. In the screenshot, you will see I’ve split the logic into three dedicated functions to keep the code clean and testable: InsertDataRow(...) UpdateDataRow(...) DeleteDataRow(...) I will include these helpers in the appendix for reference. For InsertDataRow, we use a standard SQL INSERT statement with parameters (not string concatenation), ensuring safety and better performance. INSERT INTO <tableName> (Column1, Column2, Column3) VALUES (Value1, Value2, Value3) The UpdateDataRow function uses a standard SQL UPDATE statement to modify existing records. Here’s the basic pattern: UPDATE <tableName> SET column1 = value1, column2 = value2 WHERE <condition> The DeleteDataRow function uses a standard SQL DELETE statement to remove records. Here’s the basic pattern: DELETE FROM <tableName> WHERE <condition> Now that we have done all this coding magic, what’s next? First, create an empty XFDynamicGridSaveDataResult: “Dim result as New XFDynamicGridSaveDataResult()” This step is non‑negotiable: you must send data back to the gird after the save. Without it, the grid will lose context and paging will break. That’s why this line is essential: “result.DataTable = GetDynamicGridData(si, brGlobals, workspace, args)?.DataTable” . By calling GetDynamicGridData again, you ensure the save result reflects the latest filters, sort order, and paging logic—keeping the user experience consistent after modifications. With the empty XFDynamicGridSaveDataResult created and the original data table rehydrated, the next step is to restore paging, so the user returns to the correct page after a save. Compute the current page index using VB.NET integer division: “result.PageIndex = (getDataArgs.StartRowIndex \ getDataArgs.PageSize)”. Finally, before returning the result, there’s one last piece of logic, a small but important snippet that ties everything together. This step ensures the save result object is fully populated with the data, paging info, and any additional metadata the grid needs to render correctly after modifications. result.SaveDataTaskResult = New XFDynamicGridSaveDataTaskResult() With { .IsOK = True, .ShowMessageBox = True, .Message = "Save Finished" } This allows us to assign the result to the XFDynamicGridSaveDataTaskResult. However, you will notice the “With” statement. This is a cool vb.net trick that allows you to assign a series of properties or arguments inside an enclosed block of code. Simply put, you wouldn’t have to keep assigning, result.isOk = True and so forth. This is a quick way to assign several properties that are related. This is where we assign values to the XFDynamicGridSaveDataTaskResult. You’ll notice a With block—an idiomatic VB.NET construct that lets you set multiple properties on the same object without repeating the variable name. In other words, instead of writing result.IsOk = True, result.PageIndex = …, and so forth line by line, you can group them neatly inside one block. Now that we have all this code in place, you can finally return the result. We’ve covered how to render data and how to save modified rows—but the Dynamic Grid’s most used reporting feature is its ability to apply conditional column formatting. This functionality mirrors the familiar options found in the SQL Table Editor, giving you full control over how columns look and behave based on dynamic conditions. Below is a screenshot of the SQL Table Editor column formatting properties. All these formatting properties are available in the Dynamic Grid—but only through code. You can apply them directly within the GetDynamicGridData function or encapsulate them in a dedicated formatting function for better organization and reuse. In my implementation, I chose the latter approach, creating a separate function to handle conditional column formatting. Inside the GetDynamicGridData function (see screenshot above), I added the following line: “Dim columnDefinitions As List(Of XFDynamicGridColumnDefinition) = Me.GetColumnDefinitions()”. This creates a list of XFDynamicGridColumnDefinition objects, which define the properties and formatting rules for each column in the grid. The call to Me.GetColumnDefinitions() retrieves these definitions from a dedicated function, keeping the logic clean and reusable. As you can see, this entire line of code is commented out. I wanted to highlight all the possible properties. If you look at the available properties, they match one-for-one with the properties that exist inside the SQL Table Editor component. You must initialize the variable named columnDefinition6, and as we previously discussed, the With statement is used here. Each of these properties should function exactly as they do within the SQL Table Editor. Once you have set the properties, you need to add them to the collection of column definitions. This is what you see with “columnDefinition.Add(columnDefinition#)”, which adds the specific column definition to the list of all column definitions. Finally, as with every function, the return clause simply returns the final output. In conclusion, we recognize that new code‑based components can feel intimidating at first. But with the insights from this blog, we hope we’ve lowered the barrier to entry and given you the confidence to start taking full advantage of this powerful new grid. InsertDataRow Sub Code Sample: UpdateDataRow Sub Code Sample: DeleteDataRow Sub Code Sample:
