Your answer is ok Naughton; NEVERTHELESS (and this is something that might be something wrong from my part on which comes to the database model) I have some entities whose dependency is not that linear 

I have for instance an entity "Transactions" which collects information all transactions performed in the system, let's say: sales to customers, buys from suppliers, inventory stock transactions like: physical counting, adjustments for damages, loses, etc. Also registration of orders in process (merchandise on the route which is supposed to be delivered by the supplier at an specific date). 

That entity has a lot of incoming Foreign Keys which have some kind of dependency from the same parent entities

For instance: customers and suppliers both have dependency on the "type of business (from my side not5 theirs)" "business scope (something required by the Ministry of Treasury)", "store who's buying/selling", "person who's buying/selling (from login routines)", "some accounting catalog's dependency, etc.

SO THE PROBLEM IS HERE that you can't uses sometimes the last of the cascades in the MetaData file but some of the which is in the middle of a prior chain and ALSO that some of them (dependencies FKs) must be "repeated" as to create proper cascading for some of the other entities involved inb a transaction

THIS IS BECAUSE the Cascading attribute works based on "positioning" inside the list but I rather need to have defined each one of the cascading chains in their own specific order

THAT"S WHY I created additional properties: Cascading2, Cascading3, Cascading4, Cascading5, Cascading6 and Cascading7

So I have 7 levels of cascading for any of my incoming FKs entities

BUT THE PROBLEM IS THAT I MUST rewrite  LinqExpressionHelper so it sees and do filtering accordingly

PROBLEM IS that all lamda expressions inside that class works only with one parameter for creating the "where" sentence

Do you get my point?