Skip to main content
Question

How define conditional "header" values in HTTPCaller?


ewb_fme
Contributor
Forum|alt.badge.img+4

When I specify an HTTPCaller with a defined header, then everything works as desired. However, as soon as I want to enter a conditional value (the same values that work alone), I get an error message:

 

This FME edition does not recognize the `' function. Please ensure that the current platform supports this function, the function name is spelled correctly, and that you have installed all required plug-ins.

 

Unfortunately it's the same behavior when I define conditional User Parameters and use them as HTTPCaller headers.

 

Is there a way you can use conditional "header" values in a HTTPCaller or is this a bug?

 

Best regards

8 replies

david_r
Celebrity
  • October 17, 2023

A possible workaround would be to do the conditional in an AttributeManager before the HTTPCaller, and then only reference the resulting attribute there.


ewb_fme
Contributor
Forum|alt.badge.img+4
  • Author
  • Contributor
  • October 17, 2023

Tahnk you for your answer!

I already tried this and this works. However, since I have several HTTPCallers my Workflow looks a bit chaotic when I work with "VariableSetter" and "VariableRetriever" or as you suggested with an "AttributeManager" (I use several HTTPCaller in different steps in my workflow).

 

I wish I could define the conditional value as a user parameter and use it in all my HTTPCaller. But as I stated, unfortunately I always get the above error message...


david_r
Celebrity
  • October 17, 2023

Which version is this? Have you tried with 2023.1 as well? If yes, consider reporting it as a a possible bug.


ewb_fme
Contributor
Forum|alt.badge.img+4
  • Author
  • Contributor
  • October 17, 2023
david_r wrote:

Which version is this? Have you tried with 2023.1 as well? If yes, consider reporting it as a a possible bug.

It's still version 2022.2...


david_r
Celebrity
  • October 17, 2023
ewb_fme wrote:

It's still version 2022.2...

I just tested with 2023.1, it's the same issue there. I've opened a support ticket with Safe and ask that they add their feedback here. If you want to contact Safe about it, please reference ticket id C694358.


ewb_fme
Contributor
Forum|alt.badge.img+4
  • Author
  • Contributor
  • October 17, 2023
ewb_fme wrote:

It's still version 2022.2...

@david_r​  thank you for testing this also with 2023.1! It's a quite strange behaviour in my opinion...


david_r
Celebrity
  • November 24, 2023
ewb_fme wrote:

It's still version 2022.2...

Just got the following reply from Safe regarding this issue:

We're pleased to let you know that a recent update to FME has implemented the suggestions/resolved the issues reported as:

 

             [C694358] HTTPCaller, using conditionals in the header section fails

                           Issue Summary: HTTPCaller fails when using a conditional header value

  

You will find the update in our latest FME 2024.0 beta (b24122+): safe.com/beta We expect this change to be included in the official release of FME 2024.0


ewb_fme
Contributor
Forum|alt.badge.img+4
  • Author
  • Contributor
  • November 24, 2023
ewb_fme wrote:

It's still version 2022.2...

Thank you for the update!


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings