Table of Contents

Search

  1. Preface
  2. Transformations
  3. Source transformation
  4. Target transformation
  5. Aggregator transformation
  6. Cleanse transformation
  7. Data Masking transformation
  8. Deduplicate transformation
  9. Expression transformation
  10. Filter transformation
  11. Hierarchy Builder transformation
  12. Hierarchy Parser transformation
  13. Hierarchy Processor transformation
  14. Input transformation
  15. Java transformation
  16. Java transformation API reference
  17. Joiner transformation
  18. Labeler transformation
  19. Lookup transformation
  20. Mapplet transformation
  21. Normalizer transformation
  22. Output transformation
  23. Parse transformation
  24. Python transformation
  25. Rank transformation
  26. Router transformation
  27. Rule Specification transformation
  28. Sequence Generator transformation
  29. Sorter transformation
  30. SQL transformation
  31. Structure Parser transformation
  32. Transaction Control transformation
  33. Union transformation
  34. Velocity transformation
  35. Verifier transformation
  36. Web Services transformation

Transformations

Transformations

Field rule configuration example

Field rule configuration example

You need to create a mapping to gather revenue data from multiple sales locations.
You learn that multiple fields from the upstream transformation have the same names as fields in a source transformation. To avoid field name conflicts, you decide to change the field names for all incoming fields. You decide to rename the fields so that the source is distinguishable throughout the mapping.
To increase performance, you want to ensure that the data set only includes required data. You determine that information regarding transaction dates is not required, so you decide that the date fields are not necessary for the mapping.
To change the names of all of the incoming fields, you create a field rule to rename all fields with the SalesForce_ prefix.
To exclude date fields, you create a rule to exclude fields with a date/time data type.
You review the order in which the rules appear. You realize that you want the rule to rename the fields to run after the rule to exclude the date/time fields. You move the rule to remove date/time fields so that it appears before the renaming rule.