Forum Discussion

bhalicki's avatar
bhalicki
Icon for Helper V rankHelper V
1 year ago
Solved

Shared semantic model vs local model - different results for same measure code

Hi all, Hoping someone can please explain some very odd behaviour which seems to depend on whether or not a table is created in a local model, or by direct query. I have the following tables: Pr...
Need Help
  • v-ssriganesh's avatar
    v-ssriganesh
    1 year ago

    Hi bhalicki,
    We regret the inconvenience caused and acknowledge your requirements. Please consider raising a Microsoft support ticket for further investigation. You can explain all the troubleshooting steps you have taken to help them better understand the issue.

    You can create a Microsoft support ticket with the help of the link below:
    https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket

    If this information is helpful, please “Accept as solution” and give a "kudos" to assist other community members in resolving similar issues more efficiently.
    Thank you.

     

bhalicki's avatar
bhalicki
Icon for Helper V rankHelper V
1 year ago

Hi v-ssriganesh ,

 

Thank you for getting back to me with the additional steps to try, much appreciated.

 

1 - Modifying the remote query to match the local query had no effect (using the remote DimCalendar still produced a different and incorrect result to the local DimCalendar model).

2 - Importing DimCalendarRemote into the local data model resolves the issue (however, this is not feasible as the issue I am replicating is based on how our production reporting environment is setup).  The issue appears to be triggered by the direct query DAX:
// Direct Query
EVALUATE
SUMMARIZE(
    VALUES('DimCalendarRemote'),
    'DimCalendarRemote'[MonthLong]
)


// Direct Query
DEFINE
VAR _Var0 = VALUES('DimCalendarRemote'[MonthLong])
EVALUATE
GROUPCROSSAPPLYTABLE(
    'DimCalendarRemote'[MonthLong],
    NATURALJOINUSAGE(_Var0),
    "L1",
    SUMMARIZE(
        VALUES('DimCalendarRemote'),
        'DimCalendarRemote'[Date]
    )
)

 

3 - Modifying LatestProjectMonth to hard-code the ProjectKey still produces incorrect results:

LastUpdate =

// VAR ProjectKey = SELECTEDVALUE(ProjectUpdate[Project])
VAR ProjectKey = 2
RETURN CALCULATE(MAX(ProjectUpdate[DateKey]), ALLSELECTED(ProjectUpdate), ProjectUpdate[Project]=ProjectKey)

I am not sure what else to try. It really feels like a bug.

Kind regards,

Ben.

 
v-ssriganesh's avatar
v-ssriganesh
Icon for Community Support rankCommunity Support
1 year ago

Hi bhalicki,
We regret the inconvenience caused and acknowledge your requirements. Please consider raising a Microsoft support ticket for further investigation. You can explain all the troubleshooting steps you have taken to help them better understand the issue.

You can create a Microsoft support ticket with the help of the link below:
https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket

If this information is helpful, please “Accept as solution” and give a "kudos" to assist other community members in resolving similar issues more efficiently.
Thank you.

 

  • bhalicki's avatar
    bhalicki
    Icon for Helper V rankHelper V
    1 year ago

    Thanks for your help v-ssriganesh , I have raised a ticket with Microsoft support.  Much appreciated.

    Kind regards,

    Ben.

  • bhalicki's avatar
    bhalicki
    Icon for Helper V rankHelper V
    1 year ago

    Hi v-ssriganesh , I tried to raise to Microsoft support, but they just want me to raise to their partners (which is a paid service).  They think this is a problem with the DAX, but I cannot understand why the same query should execute differently based on the data location - it really feels like a bug to me.  Do you know of a way to escalate this internally to the Microsoft product team?