Comments

5 comments

  • Best answer
    Avatar
    Ben Bauer

    Hi Ravi,

    The quickest method through the UI is:

    1. Use shift-click and/or ctrl-click to select multiple rules on a page
    2. Click 'Edit' in the page toolbar
    3. Update the [STATUS] value for each rule to 'Inactive'
    4. Click 'Save' in the page toolbar

    The quickest method through the SQL Server backend is:

    1. Connect to the SQL Server backend with a tool like SSMS (SQL Server Management Studio)
    2. Write a query that selects from the DSW.dbo.ttWaveProcessAreaObjectTargetRule table all the target rule records you wish to update
    3. Write another query that selects from the DSW.dbo.ttWaveProcessAreaObjectTargetSourceRule table all the target source rule records you wish to update
    4. Change the queries to update the [Status] field to a value of 3
    5. Execute the update queries
    6. WARNING: If steps 4 and 5 are completed incorrectly, then data could be lost or corrupted.  We don't advise operating through the SQL Server backend on a production system unless extreme caution is exercised.  The best measure is to back up the entire DSW database prior to step 5.  At the bare minimum, the 2 DSW tables in steps 2 and 3 should be backed up prior to step 5.
    Comment actions Permalink
  • Avatar
    Venkata Ravi Kumar Mullamuri

    Thank you Ben Bauer for the response!!

    Actually option 1 is not feasible for me as i need to inactivate 100's of fields , which is consuming lot of time.

    I will try the second option(through SQL) and will let you know the outcome.

    0
    Comment actions Permalink
  • Avatar
    Venkata Ravi Kumar Mullamuri

    Hi Ben Bauer,

    I can only see target rules in  DSW.dbo.ttWaveProcessAreaObjectTargetRule table, but my requirement is to inactivate source rules, can you let me know the table related to source rules?

    Thanks & Regards

    Ravi

    0
    Comment actions Permalink
  • Avatar
    Navdeep Rauli

    DSW.dbo.ttWaveProcessAreaObjectTargetSourceRule for Source Rules  

    WARNING: If steps 4 and 5 (in Ben's post) are completed incorrectly, then data could be lost or corrupted.  We don't advise operating through the SQL Server backend on a production system unless extreme caution is exercised.  The best measure is to back up the entire DSW database prior to step 5.  At the bare minimum, the 2 DSW tables in steps 2 and 3 should be backed up prior to step 5.

    0
    Comment actions Permalink
  • Avatar
    Venkata Ravi Kumar Mullamuri

    Thank you Navdeep Rauli for the response.

    0
    Comment actions Permalink

Please sign in to leave a comment.