New Composite model and Tuning query limits

amitchandak thanks for looking into this. The composite model works as a direct query and hence, all the limitations of direct query applies to it, including the possibilty of the background query of a DAX measure being evaluated for >=1M+ combinations. This is where the measure will throw an error. Despite Composite model being super cool, they are hard to maintain unless each and every measure is optimized. In my case, I had a measure with SWITCH which was throwing me the error. The moment I optimized the measure, the error went away. For a composite model to work flawlessly, it challenges the developer to write measure in a super optimized away which in turn helps the developer to take caution and apply optimization from the initial stage. I plan to work with Composite model this year to see what other challenges it throw at me, tackling which would make me become better at DAX