- edited description
- changed component to Widget - Excel Import/Export
- changed milestone to 2023_Q1
Excel not contain the correct filter values, but the correct figures in cells, after exporting from cube viewer
Describe the bug
In a cube viewer, after exporting to Excel you will have the correct figures (as shown in the view) but not the correct filter values. Usually, the values that Excel contains are the previous filter you have applied or related to the view you opened.
As a workaround, we saw that if you select the filters and after that, you click on the reload button, you will export to Excel with the filter values you selected.
To Reproduce
Steps to reproduce the behaviour:
- Go to a cube viewer and open a view.
- Change the values in the filters
- Click on Export and choose Excel
- Open the Excel exported, you will see that the values in the filter are the ones before you make the selection in step 2. But the figures in the Excel are correct as you can see in the view.
Expected behaviour
The exported Excel should contain the filter values you have chosen in the cube view.
Screenshots
In the screenshot below, the user has chosen the Default view in the cube viewer. The Default view elements are:
When we export values in cube viewer using the button excel with filter values, we see that filter values were not correct in Excel. There are no issues with cell figures.
Cubeviewer:
Excel export: these filter values are from the Default view, even if I select new elements from dimensions when I export the view the filter values were written as if the Default view is selected, however numeric cell values were the same with my selection above
Additional context
The client has the FP2 installed
We have noticed that when we click on the reload button and after that make the export, the filter values exported are correct.
Tags (select from dropdowns)
- Type: Bug
- Priority: Major
- Component: which part of the application does the issue apply to the cube viewer
- Milestone: leave blank! The scheduled quarter is to be implemented. (will be entered by support/development when responding to ticket).
- Version: select the version for which the issue is being reported (default=latest public release). Leave blank for an enhancement request.
Comments (7)
-
-
- changed status to open
Ada - I think this is already reported and a duplicate issue?
-
reporter Hi Scott,
Now that I am checking could be the 559, but I could not check with my colleague Eissa he is on leave.
Regards,
Gerardo.
-
It looks that it may be a different issue, I will check it out.
-
reporter Hey guys,
Happy new year, I hope you are well.
Is there any news about this issue? Because the customer is asking for a solution, they are in the year budgeting period.
Thanks.
Regards,
Gerardo.
-
- changed status to resolved
Hi Gerardo, Issue has been resolved and the fix will be part of the 2023.02 FP1 release.
-
- removed milestone
Removing milestone: 2023_Q1 (automated comment)
- Log in to comment