-
Field sequencing to promote zLegacyField over zField when AutoGen into Transform
For every table we’re migrating, we always build the source table data on key fields, then by applying criteria in Design we can add as many zLegacyFields as needed. When Design adds these fields, they’re usually automated into the >10k range...0 Likely to Implement
-
Update rule creation message in AutoGen from Rules Created to Process Complete
Currently this message displays when there are or aren't errors. It is misleading. Many see it and assume all AutoGen rules are created. The screen would have to be refreshed or AutoGen mappings reviewed to determine if an error occurred or not. M...0 Likely to Implement
-
Automation - zSource field missing in insert rule
Hello, Autogen won't add the zSource mandatory field in the insert rule if there is a field "SOURCE" in the design of the target table. It doesn't matter if the field is active or not. More detailed info about the issue in https://support.syniti.c...0 Likely to Implement
-
Autogen of Xref Rules should built against a snapshot rather than directly to actively maintained value mappings.
Building against a snapshot ensures a static mapping will be used for all targets throughout a complete loadcyce. This makes reconciliation of load data easier and paves the way for the addition of a load cycle concept in dspMigrate.
0
Likely to Implement
-
Increase the priority of Insert rule when Autogen registers the insert and delete rules
Currently the insert rule is registered as 20,000. Then for normal fields, it multiplies the field priority by 10 and adds the rule. Because the zLegacy fields are already automatically added to design with 1000 + the original field most of the 10...1 Likely to Implement