This is more of a work around but if your content types A and D have some common attributes then you could use the full text search to find those common attributes and save that as a view.
A better way might be to have the common attributes in a content type (for example product) and then have a reference field that can link to one of two sub-content types (clothing product detail and electronics product detail) that have the specific fields for each one. Then you would be able to have a saved view based on a field in the product content type.
A similar answer can be found here: Modeling product detail table (arbitrary key)