If the wanted selection values/searches couldn't be applied it means that there no associated data respectively no records anywhere. Nothing will change within the views and make it very clear that there are no data in regard to the last selection.
IMO this behaviour is expedient with a good balance of clarity for the users - and showed exemplarily why actions with buttons are most often a dis-improvement because the user couldn't really comprehend what the actions tries to trigger.
If the users are confused it should be considered to extend the documentation of the application and the single objects as well as to train the users to interpret the data properly. Further helpful could be re-think the entire data-model, for example to populate missing data.
Beside of this it's a not uncommon behaviour in many tools - if you take Excel with a data-set and an auto-filter and trying to filter for a non-existing value you couldn't finish this measurement because the button is out-greyed. If it are numeric values and you apply >= or similar - the behaviour changed from a selection to a query with a where-clause and then it may result in ZERO records. And that is a fundamental switch in the approach based on complete different functionality and of course with appropriate dependencies and consequences.
Pure technically you may reach a similar behaviour if you don't use selections else variables which values are then queried per if-loops within the object. I wouldn't recommend to go this way.
