View Issue Details

IDProjectCategoryView StatusLast Update
0004336SymmetricDSImprovementpublic2022-08-11 12:38
Reportermkleczek Assigned Toelong  
Prioritynormal 
Status feedbackResolutionopen 
Product Version3.11.5 
Summary0004336: Table transform should be specified per trigger_router
DescriptionMy use case is that I need to perform different transformations of the same source table depending on various circumstances. For example:

One transformation is used when a lookup transform is needed to handle foreign keys (in case of artificial primary keys in referenced tables).
The same table might be sent "as is" when it is part of a larger load when all referenced tables are part of the same load - there is no need to perform any lookup as keys match.

Right now it is not possible. What's more: the semantic of multiple table transforms applicable to a single source table is not clear (see another bug report related to this).
Tagstransformation

Activities

elong

2022-08-11 12:38

developer   ~0002155

Transforms are already specific to a table and group link, so linking to a trigger router wouldn't be any more specific.

You can use a BSH transform that looks at the channelId to run different logic for change capture versus an initial load.

Issue History

Date Modified Username Field Change
2020-04-05 18:09 mkleczek New Issue
2022-08-02 20:04 elong Tag Attached: transformation
2022-08-11 12:38 elong Note Added: 0002155
2022-08-11 12:38 elong Assigned To => elong
2022-08-11 12:38 elong Status new => feedback