Forum Discussion

MattBI's avatar
MattBI
Regular Visitor
3 years ago

Challenges with ALLSELECTED and iterators

So everything I've read says "stay away from ALLSELECTED inside iterators" because it has complex functionality and it probably won't do what you want it to (because it will activate the iterators sh...
Need Help
MattBI's avatar
MattBI
Regular Visitor
3 years ago

Hmmm...  that didn't return any results. 

I've heard that it's not a good pratice to create computed columns in a SUMMARIZE statement, so I added an ADDCOLUMNS to it, which worked, but unfortunately, that has the exact same behavior as my original measure definition.  

hnguy71's avatar
hnguy71
Icon for Super User rankSuper User
3 years ago

 MattBI, I think the answer to this also is that it really just depends on the application. If you wanted to do just a basic output then yes ADDCOLUMNS is more preferred, however, if you want to do a categorical sum or rollup then SUMMARIZE alone is sufficient. I use both methodlogy just depends on what is required for my specific circumstances.

 

If by adjusting any formula or expression making it more complicated without any clear performance gains within your model then you're doing it wrong. Just my opinion.

  • MattBI's avatar
    MattBI
    Regular Visitor
    3 years ago

    Thanks again for your response.  I hear what you're saying.  Unfortunately, as I mentioned above, using SUMMARIZE as you suggested returned no data for the rows in my output set.  Using ADDCOLUMNS instead returned results, but they were the same as what I was seeing originally so unfortunately, it didn't help improve the situation.