As an administrator, I would like to be able to backfill data that crosses over a versioning event
1. An element has an attribute that looks up information on equipment configuration (ex: a pump rate)
2. Due to an equipment change, the lookup table and the element were increased in version
3. A backfill needed to be performed on an analysis that included the attribute which changed, and the date range spans over multiple version effective dates. The desired behavior would be to use the latest version of the attribute's value since the last effective date, and the previous version of the attribute's value before the last effective date.
4. Currently, the backfill cannot go further back than the effective date of the current version.
Brent Bregenzer commented
For your specific use case, is it just the table lookup piece that is changing on the versioned element? I'm wondering if a workaround could be to include a datetime column for the effective dates in your table, and then the table lookup could utilize the "table provided time series data" setting to lookup the appropriate data based on date. This might allow you to avoid issues you've seen introduced by versioning.