I'm creating Event Frames based on a timestamp string coming from a third party system, being looked up using a table lookup data reference. I'm using the (new) generation mode 'Step Contiuous', and I'm relying on automated backfills (from my own custom service) to get the triggering to work correctly, since we can't trigger on anything else than a PI Point DR.
It turns out that the 'Step Continuous' generation mode doesn't work for my triggering input attribute when this attribute goes from having 'No Data' to getting its first value. Is this the expected behaviour when using 'Step Continuous'?
I know that 'Step Continuous' is using the HasValueChanged() function behind the scenes, and the description says "Determine if the value of an attribute or expression has changed since last evaluated during an analysis". One of my elements got its first value yesterday, so the analysis has been backfilled several times in order to catch it but it always comes out with "Events processed: 0" so it doesn't seem like the functionality catches that there's an event in the time period at all.
Is it possible to recreate the 'Step continuous' functionality in an 'Explicit trigger' mode instead? By doing that I guess we're back to the good ole "not possible to create back-to-back event frames"? I can get the EF's created but the duration is always 0 seconds (because the end date is the same as the start date)