Please Share your Product Ideas with us!

All ideas are welcome. Just because the Idea doesn't make it into the product immediately does not make it a bad idea.

dsp insert rule registration should default the target table into the 'Source Rule Table' field



Release 6.5 has modified the default value for the 'Source Rule Table' field to be the source table rather than the target table.  This is contrary to our methodology and always results in an error if you are registering a normal rule to insert the source records to the target. We should not be inserting new records to the same source we are processing, so there should not be a case where having the source table defaulted in is preferable.  We should never be self inserting, so no matter where the rule is being inserted, the field would always need to be manually overwritten – this sounds like it is not working as intended/like a bug.  If this can't be returned to the way it was, then can it become a parameter?


The Default view ( webTargetSourceRule_Def ) for the Target Source Rule page has changed from 6.3 to 6.5.   In 6.3, dbo.webTargetSource_DataSourceSel.[Target] AS SourceRuleTable .  In 6.5, it has been changed to:   dbo.webTargetSource_DataSourceSel.[Source] AS SourceRuleTable

  • Guest
  • Jan 31 2017
  • Shipped
  • Attach files
  • Admin
    Andy Lund commented
    7 Nov, 2019 01:03pm

    Hi Randall - I have checked in DSP 7.0.6 and when adding a new source rule, the default Source Rule Table is the Target Table. This was updated in 7.0.5

  • Pavlo Kurochka commented
    13 Oct, 2017 10:28pm

    I agree with JP. Should be kept like it is in 6.5.

  • John Grippa commented
    6 Jun, 2017 05:24pm

    I don't agree that this is against BOA methodology. I can think of a number of valid reasons we would register a source rule to insert into the source tables. For instance, at JnJ, their legacy system only required operations without phases on their recipe, but the target SAP system required phases. I was asked to duplicate every operation record in legacy to use as the phase record in the target. We even have built in functionality in the Transform Reconciliation to account for this by registering '+ : Adds Records' in the recon field on rule registrations.


    However, I do agree that target table should be the default value here. It was that way since CranSoft/DSW and don't see a good enough reason for having made the change. Considering there will now be people who will expect it one way or the other, I am approving this request to add a parameter in configuration where the project can decide which default they prefer. DSP would be shipped with Target as the default.  If someone would rather Source as the default they would have to manually update configuration.

  • +2