Bugs on filtering with entity alternatives

[nnhjy]

Please replicate the issue with this DB testin.zip, where the unitB with entity alternative being false in "Base" alternative will still be passed to another DB by a Merger.

[jkiviluo]

Right. It seems like alternative filter is not working as expected. Not just for the merger tool, but also for other tools and exporter. It filters parameter data, but not entities. Scenario filter does work though.

It's not just that setting entity alternative to 'false' does not filter out those entities, but all entities are always passed forward. They should not be unless they are part of the selected alternatives (either through setting true or through 'active by default' - although in case of ND entities all the parent entities should be active of course).

[soininen]

Entity alternatives have not been implemented for the alternative filter yet.

[soininen]

Alternative filter is now feature-complete.

[nnhjy]

Not sure whether it is better to open a new issue.
When there is an entity_group associated with an alternative excluded in a filter, the filtering process gets unhappy (same for the scenario and alternative filters):

...
  File "C:\Tools\Spine\Toolbox\Spine-Database-API\spinedb_api\db_mapping_base.py", line 1130, in become_referrer
    add_self_as_referrer(field_value)
  File "C:\Tools\Spine\Toolbox\Spine-Database-API\spinedb_api\db_mapping_base.py", line 1118, in add_self_as_referrer
    raise RuntimeError(f"Reference id {ref_id} in '{ref_table}' table not found")
RuntimeError: Reference id 1 in 'entity' table not found

This DB testin.zip should allow replicating the issue.