Forum Discussion

DCraneBMF's avatar
DCraneBMF
Regular Visitor
4 years ago

Default M-query parameter used to get data

Hello,   I've been struggling a bit with the M-query parameters. I created two date parameters (start/end) in the power query editor.  In my report I created two datetables and bound these to the ...
Need Help
DCraneBMF's avatar
DCraneBMF
Regular Visitor
4 years ago

Hi jbwtp,

 

Yes I'm following something like that. Not the same link, but something like that. 

I've tried a calculatetable, but the results is the same. As long as I keep the calculate functions within the actual table all is good. The moment I try to make a new one it uses the parameters set in the query-editor. 

 

Thank you for your help. I'm going to keep trying to see if I can solve it somehow. If I find out something I'll post it here. 

 

Regards,

 

Den

jbwtp's avatar
jbwtp
Memorable Member
4 years ago

Hi Den,

 

I think the reason could be that you are creating a new table (via CREATETABLE or otherwise) and the filter is set on the original one. Because it is not a "true" PQ filter which is set at in a query and is dynamic and fold in the SQL query at runtime when the slicer/filter updates, I think, PBI engine just does not know that it exists when doing another table to whcih your slicer kind of does not apply. May by try explicitely forcing it via FILTER when doing SUMMARIZE or CREATETABLE?

 

Kind regards,

John