I have encountered a gap in ADO's filtering capabilities for transformation views that I believe many integration professionals share.
When working with source data, it is common to receive files that contain codes — currency codes, cost center codes, product codes — that are not relevant to the current Anaplan setup. Importing those rows is redundant at best and causes import errors at worst. The logical solution is to filter the source data against the lists already configured in Anaplan before the data ever reaches the model.
Currently, this is not possible natively. The workaround — joining transformation views to replicate the validation logic — is functional but time-consuming to set up and maintain. The alternative is to ignore the errors, which is not an acceptable approach in a production environment.
ADO does include a list-based filter condition when configuring pipeline validations, but the "list" in question is a static set of values entered manually — for example, typing out EUR, USD, DKK. This may be workable for small, stable datasets, but it does not scale. An organization with hundreds of cost center codes cannot realistically maintain a static list, and any change to the Anaplan list would require a manual update to the filter as well.
The request is straightforward: allow ADO transformation view filters to reference Anaplan list dimensions directly as a filter condition. This would make validation dynamic, reduce setup effort significantly, and align the integration layer more closely with the model it is feeding.
This is something I encounter daily when working with ADO, and I am confident it is a common pain point for anyone doing serious integration work on the platform.
