Skip to main content
Solved

Conditional Parameter Problem

james_c_452
Supporter
Forum|alt.badge.img+7

Hi,

I have a parameter that I have set in an FME Server/Flow app that is conditional on another parameter. I.e. The first is set by the user in an app. If there is a certain value, then it would require you two set a secondary variable.

I used to have this set as a simple ‘dropdown’ choice, which then would require a simple text input (if needed). I tried to change the original parameter to a ‘choice list’ instead, to make it easier to follow, but this is causing me issues.

When I preview how this looks in FME Form it works exactly how I want to. Though when I try to on Flow it doesn’t show/require the secondary parameter. 

Is this a bug? Or something I can fix? I am constrained to version 2023.2.1.0 (23774) for at least the foreseeable future

Any advice would be appreciated, I can’t seem to get it to work no matter what I try

Best answer by luke.hicks

I can confirm that this is a bug on all current versions of FME Flow (up to 2024.2.2 as of today). Unfortunately for now, users will have to use the “Dropdown” configuration for Choice Parameters if they intend to use the Choice Parameter as a Conditional Visibility signifier in another User Parameter for FME Flow Apps.

The development team has been notified of this bug. The internal issue number is “FMEFLOW-24874”.

View original
4 Attachments
Did this help you find an answer to your question?
This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

3 replies

j.botterill
Influencer
Forum|alt.badge.img+34
  • j.botterillInfluencer
  • Influencer
  • January 31, 2025

Might be best to lodge this directly to Safe software, if it is indeed a bug. https://support.safe.com/hc/en-us/p/Support

I searched the change log and found this, but might be under related  https://fme.safe.com/changelog/?_search=conditional%20parameters&_change_log_product=fme-flow%2Cfme-form&_change_log_version=2021020200%2C2024020200

Try setting a default value for the dropdown choice. Also changing enabling the required or not required option 

 

james_c_452
Supporter
Forum|alt.badge.img+7
  • james_c_452Supporter
  • Author
  • Supporter
  • January 31, 2025

Thanks for the reply ​@j.botterill 
That change log does seem to be what I am looking for, perhaps, I’m stuck with build 23774 for the time being unfortunately.
I have tried your other suggestions, they didn’t work either :(

luke.hicks
Safer
Forum|alt.badge.img+8
  • luke.hicksSafer
  • Safer
  • Best Answer
  • February 3, 2025

I can confirm that this is a bug on all current versions of FME Flow (up to 2024.2.2 as of today). Unfortunately for now, users will have to use the “Dropdown” configuration for Choice Parameters if they intend to use the Choice Parameter as a Conditional Visibility signifier in another User Parameter for FME Flow Apps.

The development team has been notified of this bug. The internal issue number is “FMEFLOW-24874”.

Most helpful members this week

Community Stats

30,846
Posts
116,935
Replies
38,669
Members
Terms & ConditionsCookie settings

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
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.