Hi Alec,

Could you post us some sample idea so we can get a better idea of what your trying to do?

Thanks

Sure. Currently in a record filter you have to input a specific value to check against. E.g. you would say 'accept all records where Date > 1-Jan-2012', where Date is a field in my data. I wish to be able to say 'accept all records where Date > Start Date' where Start Date is another field in my data.

Essentially this is just enforcing a relationship between two fields, i.e. enforcing a schema for my data and removing any invalid records.

Specific example: Say I am analysing the performance of one or more online advertising campaigns, obtaining my data from the DoubleClick feed. Each one will have a Campaign Start Date when all of the adverts officially go live. However, some testing will be carried out beforehand and so when collecting 'All Available Data' there will be records returned from before the start date. These records must be filtered out as they are not valid, and including them would make any analysis inaccurate.

Alec - If you define a formula that compares two or more values in the data set (including even an externally-managed Variable), the true/false result of that formula field that enforces your schema can be either "IN" or "OUT". You can then define a Named Query to accept only the "INs" and set each view's visible data subset to be Filtered Data (IN) intersected with "Query=IN" only. All these schema-enforcing fields can be hidden.

Thanks tj, that's what I have done for the moment - it would still be a nice feature though if only to make the process less manual