Error in Excel when using slicers and updating data

[Joakim Gröndahl]

Hi,

I'm running Saike CE 3.6 with Mondrian and I'm using XMLA_Provider_v1.0.0.103 to fetch data to Excel (Office 365).

If I create a pivot table from the data source, add a slicer and update the data I get an error message in Excel and the following error in the saiku logs.

2016-09-23 14:50:02,718 ERROR [mondrian.xmla.XmlaServlet] Errors when handling XML/A message
mondrian.xmla.XmlaException: XMLA MDX parse failed
...
Caused by: mondrian.olap.MondrianException: Mondrian Error:Failed to parse query 'with set __XLUniqueNames as { [dim_vendors].[Vendor Hiearchy].[All V
endors] }
set __XLDrilledUp as
Generate(__XLUniqueNames,
{ IIF([dim_vendors].CAST( [Vendor Hiearchy].currentmember.Properties("LEVEL_NUMBER") AS INTEGER ) <= 2147483647,
        [dim_vendors].[Vendor Hiearchy].currentmember,
        Ancestor([dim_vendors].[Vendor Hiearchy].currentmember,
                        [dim_vendors].CAST( [Vendor Hiearchy].currentmember.Properties("LEVEL_NUMBER") AS INTEGER ) - 2147483647)) } )
member [Measures].__XLPath as
Generate(
        Ascendants([dim_vendors].[Vendor Hiearchy].currentmember),
                                [dim_vendors].[Vendor Hiearchy].currentmember.UniqueName,
                                "__XLPSEP")
select { [Measures].__XLPath } on 0,
__XLDrilledUp on 1
from [Transaction Cube]

I've tried switching around what dimensions I add slicers for and what data I use with the same result.

I can't quite figure out what the problem is. Is it related to my data, cube definition or something else?

Best regards,

/Joakim

[Alexandra Davidoiu (Iancu)]

Hi,

Sorry for the late response. I need the hole log file. The problem is from Mondrian, but from your post I can't see what the problem is with this querry.

Best regards,
Alexandra

[hassoalbert]

Encountering errors in Excel while using slicers and updating data can be frustrating and disrupt workflow efficiency. One common issue is when slicers fail to update properly after data changes. This can happen if the data source range is not correctly defined or if there are discrepancies between the slicer settings and the underlying data. Additionally, errors may occur if there are inconsistencies in the workbook structure or if the Excel file is corrupted. It's essential to double-check the slicer settings, refresh data connections, and ensure compatibility with the Excel version being used. Sometimes, optimizing the workbook's memory usage and performance by reducing unnecessary elements or splitting large datasets in appwizardpro.co.nz may help alleviate errors. If the problem persists, seeking assistance from Excel support forums or consulting with colleagues experienced in Excel troubleshooting can provide further insights and potential solutions to resolve the errors efficiently.

[hassoalbert]

When using slicers in Excel to filter data, you might encounter errors if the data source or the pivot table is updated. This often happens if the slicers are linked to a pivot table that has been altered or if the underlying data has changed in a way that affects the slicer's functionality. Common issues include slicers not updating correctly, showing outdated data, or causing Excel to freeze or crash. To resolve these issues, ensure that the data source is correctly connected, refresh the pivot table after any data updates, and verify aethersx2apk that the slicers are appropriately linked to the updated pivot table. If problems persist, you might need to recreate the slicers or pivot table to resolve any inconsistencies.