I'm really-really late to this party, but I just experienced something similar recently, and I'd like to comment...
What could have been a real bug in early 2015 (I assume it's fixed by now), may still be a problem, only of a different kind...
Transition to derived fields requires a slightly different approach to using these fields in set analysis. The difference is the most evident with the field Year.
Traditionally, we calculated Year as a numeric field in our Master Calendar:
Year(Date) as Year
The default derived field Year is not calculated as a Dual field:
Dual(Year($1), YearStart($1)) as Year (I'm quoting from memory).
So, the same numeric filters as we always used for the "traditional" field Year, will not work with the derived field Year. Instead, we should use Advanced Search and apply the Year() function there in order to enable numeric comparison.
I'll try to research this topic a bit more and post a blog about it.