Table of Contents

Search

  1. Preface
  2. Introduction to Data Validation Option
  3. Repositories
  4. XML Data Source
  5. Tests for XML Data Sources
  6. Connections
  7. Expressions
  8. Table Pairs
  9. Tests for Table Pairs
  10. Single-Table Constraints
  11. Tests for Single-Table Constraints
  12. Examples of Tests from Spreadsheets
  13. SQL Views
  14. Lookup Views
  15. Join Views
  16. Aggregate Views
  17. Business Intelligence and Reporting Tools Reports
  18. Dashboards
  19. DVOCmd Command Line Program
  20. Troubleshooting
  21. Appendix A: Datatype Reference
  22. Appendix B: Reporting Views
  23. Appendix C: Metadata Import Syntax
  24. Appendix D: Jasper Reports
  25. Appendix E: Glossary

Data Validation Option User Guide

Data Validation Option User Guide

Overriding XML Source File Information

Overriding XML Source File Information

There can be multiple XML files that match an XML definition and need to be tested, similar to flat files. There may be one flat file source or target definition, but there may be multiple flat files with data that are used for testing.
When a Join View is used to flatten an XML structure, it becomes a general definition to process any XML file that conforms to that structure. Thus, the file location and the file name can change even if they are specified in the original dialog used to create the Join View. It is possible to use the same Join View definition to process any file that conforms to that structure.
To use the same name, the path and file name specified in the connection can be over-ridden when the Join View is used in a Table Pair or Single Table. Click the Conn A or Conn B button to show and edit the Connection details.
Only Join Views that flatten a single XML structure and do not include any other tables or files can be over-ridden this way. If the Join View includes other objects or tables, the over-ride is not possible.

0 COMMENTS

We’d like to hear from you!