Skip to content

Automagically detect issues where filter and batching dates don't play nicely [Magalie] #1407

@tznind

Description

@tznind

Is your feature request related to a problem? Please describe.
Batching was set up on a dataset for 10 years but the filter in the dataset was defined for 11 years. It would be nice if RDMP told me that batching start date was inside the filter window (as a warning).

Describe the solution you'd like
Rather than users entering SQL every time and in order to validate stuff like batching dates. We should have a logical filter where user just chooses date and field and then we store that and generate readonly SQL automatically (and parameters).

Then we can pick up this specific type of filter and rationalise the dates with other systems e.g. batching

RDMP should automagically detect when filters and batching dates are incompatible with one another or likely to result in missing data

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions