Skip to main content
Solved

Custom Method in Object Connection Transformation

  • November 24, 2020
  • 5 replies
  • 295 views

Forum|alt.badge.img+4

How to pass values of target key reference to my custom method as parameter.

Best answer by Mathias Dahl

This is all documented in the end-user documentation.

This topic has been closed for replies.

5 replies

Mathias Dahl
Superhero (Employee)
Forum|alt.badge.img+32
  • Superhero (Employee)
  • November 25, 2020

How to pass values of target key reference to my custom method as parameter.

I suggest that you look at any of the many existing transformation methods that are installed by default. Your method is called automatically.

 


Forum|alt.badge.img+4
  • Author
  • Do Gooder (Customer)
  • November 25, 2020

Hi,

Thanks for the update, would appreciate if possible to share any documentation related to the same.


Mathias Dahl
Superhero (Employee)
Forum|alt.badge.img+32
  • Superhero (Employee)
  • Answer
  • November 25, 2020

This is all documented in the end-user documentation.


Forum|alt.badge.img+4
  • Author
  • Do Gooder (Customer)
  • November 25, 2020

Thanks found the details in the documentation.

 

“For some scenarios it is not possible to map the target and source columns due to the fact that the source columns are not included in the target database view. You then have two options which both require some programming work. You can either extend the target view with the necessary columns or create a stored function that makes the actual key transformation. The name of the function should in this case be registered as the transformation method. Note that it should also hold the package name, e.g. My_Package_API.My_Transformation. It needs to be defined as a function that returns a string value. It also requires two values in parameters (strings); the Target Key Reference and the Service Name (in that specific order).”


Mathias Dahl
Superhero (Employee)
Forum|alt.badge.img+32
  • Superhero (Employee)
  • November 25, 2020

Thanks found the details in the documentation.

 

“For some scenarios it is not possible to map the target and source columns due to the fact that the source columns are not included in the target database view. You then have two options which both require some programming work. You can either extend the target view with the necessary columns or create a stored function that makes the actual key transformation. The name of the function should in this case be registered as the transformation method. Note that it should also hold the package name, e.g. My_Package_API.My_Transformation. It needs to be defined as a function that returns a string value. It also requires two values in parameters (strings); the Target Key Reference and the Service Name (in that specific order).”

Great, then you are now an expert! (few reads our documentation) :)