Table of Contents

Search

  1. Preface
  2. Introduction to Transformations
  3. Transformation Ports
  4. Transformation Caches
  5. Address Validator Transformation
  6. Aggregator Transformation
  7. Association Transformation
  8. Bad Record Exception Transformation
  9. Case Converter Transformation
  10. Classifier Transformation
  11. Comparison Transformation
  12. Consolidation Transformation
  13. Data Masking Transformation
  14. Data Processor Transformation
  15. Decision Transformation
  16. Duplicate Record Exception Transformation
  17. Expression Transformation
  18. Filter Transformation
  19. Hierarchical to Relational Transformation
  20. Java Transformation
  21. Java Transformation API Reference
  22. Java Expressions
  23. Joiner Transformation
  24. Key Generator Transformation
  25. Labeler Transformation
  26. Lookup Transformation
  27. Lookup Caches
  28. Dynamic Lookup Cache
  29. Macro Transformation
  30. Match Transformation
  31. Match Transformations in Field Analysis
  32. Match Transformations in Identity Analysis
  33. Normalizer Transformation
  34. Merge Transformation
  35. Parser Transformation
  36. Python Transformation
  37. Rank Transformation
  38. Read Transformation
  39. Relational to Hierarchical Transformation
  40. REST Web Service Consumer Transformation
  41. Router Transformation
  42. Sequence Generator Transformation
  43. Sorter Transformation
  44. SQL Transformation
  45. Standardizer Transformation
  46. Union Transformation
  47. Update Strategy Transformation
  48. Web Service Consumer Transformation
  49. Parsing Web Service SOAP Messages
  50. Generating Web Service SOAP Messages
  51. Weighted Average Transformation
  52. Window Transformation
  53. Write Transformation
  54. Appendix A: Transformation Delimiters

Developer Transformation Guide

Developer Transformation Guide

Run-Time Properties

Run-Time Properties

You can configure the following Write transaction properties on the Run-time tab:
Connection
Available for relational targets. Connection used by the transformation. Click in the right side of the field to change the connection.
The following image shows the location of the dropdown button to click:
Click the right side of the Connection name field to change the connection that the transformation uses.
Reject truncated/overflow rows
Available for relational and customized targets.
The Developer tool lets you convert data by passing it from port to port. Sometimes a conversion causes an overflow of numeric data or truncation of strings in columns that contain characters. For example, passing data from a Decimal (28, 2) to a Decimal (19, 2) port causes a numeric overflow. Likewise, if you pass data from a String(28) port to a String(10) port, the Data Integration Service truncates the strings to 10 characters.
When a conversion causes an overflow, the Data Integration Service, by default, skips the row. The Data Integration Service does not write the data to the reject file. For strings, the Data Integration Service truncates the string and passes it to the next transformation.
Select this option to include all truncated and overflow data between the last transformation and target in the session reject file. The Data Integration Service sends all truncated rows and any overflow rows to the session reject file or to the row error logs, depending on how you configure the session.
Reject file directory
Directory where the reject file exists. Default is the RejectDir system parameter.
Reject file name
File name of the reject file. Default is <output_file_name>.bad.
If multiple partitions write to the flat file target, each partition writes to a separate reject file named <output_file_name><partition_number>.bad.

0 COMMENTS

We’d like to hear from you!