Return a radio option name, not value.. can we do it??

[ab_cdef]

Hi

When using Fusion to fetch a radio or checkbox field, Fusion always retrieves the option's value rather than its name. For example, if a radio option is named "Consumers" with a value of "CONS," Fusion returns "CONS" by default.

Is there a way to get Fusion to return the option name, "Consumers", for use in downstream processing?

[lgaertner]

Hello,

I think you need to clarify your question a bit more, as in my understanding this behaviour is common sense.
You fetch the stored information concerning a specific object (Task, Project, ...) and get back the fields and their values for this dataset. The returned data comes as key value pairs.

Regards

Lars

[ab_cdef]

@lgaertner So I have the following field:

At the moment, Fusion only returns the value "CONS", and I'm unsure how to configure it to return "Consumers" using Fusion.

[D____D]

The system value is the only value that's passed from Workfront fields to Fusion when querying those fields in Fusion. If your system values differ from your display values, then set your display and system values to match if that's okay.  Sometimes, when designing forms/fields, you need the users to see one thing versus what it actually is, but in some cases, you need it to match. The choice is yours based on your requirements.

[ChrisStephens]

You can get it, but not from the original object. Once you have the value you want, you should be able to make a request to the POPT end-point, parameter:name = {field}, and value = {value}.

[ab_cdef]

This is interesting… but it also means that every time I want to retrieve the name, I'd have to make an API request. It would be great if this could be mapped directly in the Workfront modules.

[Sven-iX · Accepted solution]

Hi @ab_cdef  (nice username!)

To combine Chris' and John's responses, you could, somewhere at the beginning of the scenario, get all the parameters options (label & value) and then you'd have a lookup object

Sorry - meant to attach the JSON

[ab_cdef]

This goes beyond what I expected - thank you so much for taking the extra effort to create this JSON! I'll import it and play around with it .

Really appreciate it - thanks again! @Sven-iX 

[JohnJOSullivan]

A quick and dirty way would be to use a switch module:

Example: A field we use whose value doesn't match its label: