All ideas are welcome. Just because the Idea doesn't make it into the product immediately does not make it a bad idea.
We need to be able to register a target multiple times in the same object in Transform, but there appears to be a constraint that does not allow us to do so. We have thought of a few workarounds that will allow us to accomplish what we need:
1. Create a new target table with a suffix for each subsequent instance. Each instance would require an insert rule and its own rules and naming convention.
2. Create a view of the target table named with a suffix on the table name. We could write rules against the same target table, but would have to use different naming conventions.
3. Create a dummy target with an '_' appended to the end of the name. This would allow us to maintain the naming convention for all rules, reports, and exports, but would not be applicable if more than two instances of the target are required.
However, all of these options greatly convolute the process and would make any transition to new resources much more complicated than necessary. We come across situations like this all the time requiring processing of a target followed by processing other targets and then processing the initial target to insert or update records based on the other tables. Please consider removing the constraint from Transform in a future release.
Guest
