- changed status to open
Full MDX query gets modified and broken by Apliqo UX
Issue #772
resolved
When providing a full MDX query to a grid widget, Apliqo decides to remove the measure dimension and by doing so, it breaks the query.
Attached below are:
1. the original query which works fine in Arc
2. the resulting query which is being fired from UX. In the second code snippet at line 37 you can see that the measure is completely missing and there is a rogue comma in the query
WITH
SET [IHH Vol]
AS {[Depot].[Depot].[IHH Strukt],
[Depot].[Depot].[IHH Warrants],
[Depot].[Depot].[IHH Mgmt]}
MEMBER [Depot].[Depot].[IHH Vol] AS SUM([IHH Vol])
SELECT {{
[Depot].[Depot].[IHH Strukt],
[Depot].[Depot].[IHH Warrants],
[Depot].[Depot].[IHH Mgmt],
[Depot].[Depot].[IHH Vol]
}} ON ROWS,
{{TOPCOUNT({[Underlying].[Underlying].[Stock_Type].children, [Underlying].[Underlying].[MarketIndex_Type].children}, 5,
[PnlUnderlying].([MeasurePnlUnderlying].[MeasurePnlUnderlying].[Risk_Vega],
[Depot].[Depot].[IHH Vol],
[Moneyness].[Moneyness].[TOTAL_MONEYNESS],
[Maturity].[Maturity].[TOTAL_MATURITY],
[Version].[Version].[LAST_OR_LAST_REPORTED],
[SourceSystem].[SourceSystem].[TOTAL_SOURCESYSTEM],
[Currency].[Currency].[TOTAL_CURRENCY],
[Instrument].[Instrument].[TOTAL_INSTRUMENT],
[Portfolio].[Portfolio].[TOTAL_PORTFOLIO],
[Time].[Time].[$<<platin1.Time.Time>>]))},
{BOTTOMCOUNT({[Underlying].[Underlying].[Stock_Type].children, [Underlying].[Underlying].[MarketIndex_Type].children}, 5,
[PnlUnderlying].([MeasurePnlUnderlying].[MeasurePnlUnderlying].[Risk_Vega],
[Depot].[Depot].[IHH Vol],
[Moneyness].[Moneyness].[TOTAL_MONEYNESS],
[Maturity].[Maturity].[TOTAL_MATURITY],
[Version].[Version].[LAST_OR_LAST_REPORTED],
[SourceSystem].[SourceSystem].[TOTAL_SOURCESYSTEM],
[Currency].[Currency].[TOTAL_CURRENCY],
[Instrument].[Instrument].[TOTAL_INSTRUMENT],
[Portfolio].[Portfolio].[TOTAL_PORTFOLIO],
[Time].[Time].[$<<platin1.Time.Time>>]))}} ON COLUMNS
FROM [PnlUnderlying]
WHERE ( [Portfolio].[Portfolio].[TOTAL_PORTFOLIO],
[Instrument].[Instrument].[TOTAL_INSTRUMENT],
[Currency].[Currency].[TOTAL_CURRENCY],
[SourceSystem].[SourceSystem].[TOTAL_SOURCESYSTEM],
[Version].[Version].[LAST_OR_LAST_REPORTED],
[Maturity].[Maturity].[TOTAL_MATURITY],
[MeasurePnlUnderlying].[MeasurePnlUnderlying].[Risk_Vega])
WITH SET [IHH Vol]
AS {[Depot].[Depot].[IHH Strukt],
[Depot].[Depot].[IHH Warrants],
[Depot].[Depot].[IHH Mgmt]}
MEMBER [Depot].[Depot].[IHH Vol] AS SUM([IHH Vol])
SELECT
{{TOPCOUNT({[Underlying].[Underlying].[Stock_Type].children, [Underlying].[Underlying].[MarketIndex_Type].children}, 5,
[PnlUnderlying].([MeasurePnlUnderlying].[MeasurePnlUnderlying].[Risk_Vega],
[Depot].[Depot].[IHH Vol],
[Moneyness].[Moneyness].[TOTAL_MONEYNESS],
[Maturity].[Maturity].[TOTAL_MATURITY],
[Version].[Version].[LAST_OR_LAST_REPORTED],
[SourceSystem].[SourceSystem].[TOTAL_SOURCESYSTEM],
[Currency].[Currency].[TOTAL_CURRENCY],
[Instrument].[Instrument].[TOTAL_INSTRUMENT],
[Portfolio].[Portfolio].[TOTAL_PORTFOLIO],
[Time].[Time].[20240131]))},
{BOTTOMCOUNT({[Underlying].[Underlying].[Stock_Type].children, [Underlying].[Underlying].[MarketIndex_Type].children}, 5,
[PnlUnderlying].([MeasurePnlUnderlying].[MeasurePnlUnderlying].[Risk_Vega],
[Depot].[Depot].[IHH Vol],
[Moneyness].[Moneyness].[TOTAL_MONEYNESS],
[Maturity].[Maturity].[TOTAL_MATURITY],
[Version].[Version].[LAST_OR_LAST_REPORTED],
[SourceSystem].[SourceSystem].[TOTAL_SOURCESYSTEM],
[Currency].[Currency].[TOTAL_CURRENCY],
[Instrument].[Instrument].[TOTAL_INSTRUMENT],
[Portfolio].[Portfolio].[TOTAL_PORTFOLIO],
[Time].[Time].[20240131]))}} ON COLUMNS,
{{
[Depot].[Depot].[IHH Strukt],
[Depot].[Depot].[IHH Warrants],
[Depot].[Depot].[IHH Mgmt],
[Depot].[Depot].[IHH Vol]
}} ON ROWS
FROM [PnlUnderlying]
WHERE (
,
[Maturity].[Maturity].[TOTAL_MATURITY],
[Version].[Version].[LAST_OR_LAST_REPORTED],
[SourceSystem].[SourceSystem].[TOTAL_SOURCESYSTEM],
[Currency].[Currency].[TOTAL_CURRENCY],
[Instrument].[Instrument].[TOTAL_INSTRUMENT],
[Portfolio].[Portfolio].[TOTAL_PORTFOLIO]
)
Comments (2)
-
-
- changed status to resolved
Issue has been resolved and the fix will be part of the 2024 Feb release
- Log in to comment
Issue is currently under investigation