Table of Contents

Search

  1. Preface
  2. Introduction to Test Data Management
  3. Test Data Manager
  4. Projects
  5. Policies
  6. Data Discovery
  7. Creating a Data Subset
  8. Performing a Data Masking Operation
  9. Data Masking Techniques and Parameters
  10. Data Generation
  11. Data Generation Techniques and Parameters
  12. Working with Test Data Warehouse
  13. Analyzing Test Data with Data Coverage
  14. Plans and Workflows
  15. Monitor
  16. Reports
  17. ilmcmd
  18. tdwcmd
  19. tdwquery
  20. Data Type Reference
  21. Data Type Reference for Test Data Warehouse
  22. Glossary

Conditional Constraints and Data Conflicts

Conditional Constraints and Data Conflicts

When you perform a data generation operation, there might be conflicts between the conditional constraint and the values specified in the data generation rule parameters. The data generation operation prioritizes the data generation rule over the conditional constraint and TDM generates data with warning messages.

Conditional Constraints and Data Conflicts Example

You want to generate data in the Created_Date and Modified_Date columns in an Employee table. You create a random generation rule with a date range from January 1, 1970 to July 31, 2014, and assign the rule to both Created_Date and Modified_Date columns. You want the value in the Modified_Date column to be greater than the value in the Created_Date column. You create a conditional constraint and enter the following expression in the
Expression Builder
:
Modified_Date > Created_Date
When the Created_Date column contains July 31, 2014, TDM cannot generate data that adheres to the conditional constraint because the data generation rule parameters restrict the end dates to July 31, 2014. TDM generates a date within the specified range in the Modified_Date column and generates warning messages.
The following table lists sample employee details with generated data:
Employee ID
Created_Date
Modified_Date
1111
7/31/2014
1/13/2002
2111
6/5/2000
5/6/2010
8112
7/31/2014
5/16/1990