Reference set members with effectiveTime older than latest version of parent code system are ignored on RF2 import

[jonmdtn]

Hi there, we have some issues trying to load our extension and derivative history on version 10.5.1 of Snowstorm. Previously, on v8.3.0, we could load any data from an RF2 into any destination branch for the most part. However, in version 10.5.1 there seems to be some filtering of reference set members imported using RF2 to prevent loading members that are already loaded. And I assume it does this by comparing effectiveTime due to some log messages shown when importing. I think this might be caused by the fact that we version our national extension and derivatives with the same effectiveTime, while the derivative code system branch is a child of our national code system branch.

With a full history of international edition and national extension, when trying to import our refset RF2s onto the child branch of the national extension, it will only ever add members with an effectiveTime later than the latest version of our national extension. We got this hunch from a log message and ended up rolling back our national extension to prove it.

We have purposefully disconnected our refset history and code system versions, so we want to load all historical data for a specific derivative into a 20240915 version. This needs to be dependant on the 20240915 version of our national extension. However when doing this, we can only get members with effectiveTime later than 20240915 to load. We can tell Snowstorm is reading all the members, so I'm hoping we've just missed some configuration value her but I didn't find anything special in the application.properties for this, nor any mention of this feature in the changelogs.

Is this the intended behavior, and is there a simple way around it? If not, are there any known workarounds to get the data correct?

Thanks in advance, jonmdtn