0040416: ResourceLocationRouter overrides standard router, provide override/extension mechanism

Description

The location needs to be routed taking into account standard retail tables as well as sometimes custom tables.
An example is the resource location foreign key. The location should also be routed to the orgs of the resource.

However, currently we can only define one router per table. For the location table this router should normally defined in the standard retail sync module. This does not allow us to take into account custom modules like resource characteristics.

Steps To Reproduce

Symmetric ds with retail sync and resource sync module

Proposed Solution

Provide an extension or override mechanism.

For example allow defining multiple synchronized table records for the same table but only use the one with highest priority.

Issue History
Date Modified	Username	Field	Change
2019-03-19 12:42	mtaal	New Issue
2019-03-19 12:42	mtaal	Assigned To	=> mtaal
2019-03-19 12:42	mtaal	Triggers an Emergency Pack	=> No
2022-05-20 09:06	mtaal	Status	new => closed

Relationships [ Relation Graph ] [ Dependency Graph ]

Notes
There are no notes attached to this issue.