Dynamic Routes Event Trigger limitation on per-database multi-tenant architecture

[gloredo]

In a per-database multi-tenant model if Dynamic Routes are used to direct the consumer to its specific DB theoretically each consumer should be a member of the connection set and not fire Event Triggers, making the functionality useless. Did I miss any part? Because the way I see what can be done in terms of business rules will be limited to Actions and Remote Schemas.