Table of Contents

Search

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

Transformations

Transformations

Hybrid macros

Hybrid macros

A hybrid macro expands an expression both vertically and horizontally. A hybrid macro generates a set of vertical expressions that also expand horizontally.
Configure a hybrid macro based on your business requirements. Use the configuration guidelines for vertical and horizontal macros to create a hybrid macro.

Example

For example, the following expression uses the %OPR_IIF% horizontal expansion function to convert the format of the date fields represented by the %dateports% macro input field to the 'mm-dd-yyyy' format:
%OPR_IIF[IS_DATE(%dateports%,%fromdateformat%),TO_STRING(TO_DATE(%dateports%,%fromdateformat%),'mm-dd-yyyy'),%dateports%]%
The %fromdateformat% macro input field defines the different date formats used in the date fields: mm/dd/yy and mm/dd/yyyy.
At run time, the application expands the expression vertically and horizontally, as follows:
IIF(IS_DATE(StartDate,’mm/dd/yy’),TO_STRING(TO_DATE(StartDate,’mm/dd/yy’),’mm-dd-yyyy’), IIF(IS_DATE(StartDate,’mm/dd/yyyy’),TO_STRING(TO_DATE(StartDate,’mm/dd/yyyy’),’mm-dd-yyyy’), StartDate)) IIF(IS_DATE(EndDate,’mm/dd/yy’),TO_STRING(To_Date(EndDate,’mm/dd/yy’),’mm-dd-yyyy’), IIF(IS_DATE(END _DT,’mm/dd/yyyy’),TO_STRING(TO_DATE(EndDate,’mm/dd/yyyy’),’mm-dd-yyyy’), EndDate))
The expression expands vertically to create an expression for the StartDate and EndDate fields that %dateports% represents. The expression also expands horizontally to use the constants that %fromdateformat% represents to evaluate the incoming fields.

0 COMMENTS

We’d like to hear from you!
Patrick Dwyer - June 05, 2023

The example shows the "IsDate" function. This should be corrected to "Is_Date" function.

Informatica Documentation Team - June 05, 2023

Hi Patrick Dwyer,

You are correct. Thanks so much for bringing this to our attention! We'll fix it in the next major release.