Jump to content

ICF static radioset Display is stored - not Value - when directly specifying the custom field as Field ID. Is that right?


Recommended Posts

Posted

We have this in the ICF:

image.thumb.png.2335d0fad3973a42d992be755dc3ce1d.png

The value of h_custom_c that is stored in the Request is the Display not the Value. This doesn't seem right to me, by very definition. The Display should be (only) what the user sees and the Value should be what is stored in the system. Is this by design or an error?

I have needed to put-in a workaround as an update Custom Field node that switches this in the workflow to the Value: &[functions.pcf("problemDetails","h_custom_c_value")]

Posted

+1

I have the same issue with a static checklist.

Sometimes the values that are input by the user are not even set in the custom field referenced in the field ID.

In general, I try and avoid the use of Checklists and Radio options because of this.

As a workaround, I have a decision node in my workflow which checks if the custom field is either not set, or contains any of the display values - if any of these conditions are true, it forces an update of the custom field with the ICF _value option. 

Posted

This is by design, and mapping the *_value from the Capture to a Custom Field in the Workflow is the correct method where you wish to use the value.

One of many reasons is that this allows you to have values of "1, 2, 3, 4, 5" to ensure the Displayed Values are in the correct order, whilst still allowing meaningful values in the Custom Fields for displaying to viewers of the Request, and for maintaining Workflows without having to look up what the numbers really mean.

  • 2 weeks later...
Posted

What I also found is that its different for Tasks - the IC stores the Display Value but when you use the same process with a Task it uses the Value, which can be a bit confusing 

Posted
On 01/08/2024 at 10:06, Gareth Cantrell said:

I have the same issue with a static checklist.

Sometimes the values that are input by the user are not even set in the custom field referenced in the field ID.

The Display value for a Checklist is a comma-separated list of the selected options, as 0, 1, or multiple selections can be made.
Radio Buttons store the Display Value of the selected option in the usual way.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...