Flow designer is creating a new choice value instead of using the existing one.

[adish]

Hello, 

I have created a flow in flow designer where the flow is creating a new value for state field (for example) instead of using the existing field value. The field appears to be blue in color.

As an example, in the screenshot below,  We can see 2 Requested previously choices and the blue one is created by flow. I'd like to map these 2 choices so that we don't see the blue coloured choice.

Can anyone please help? 

[Saurabh Gupta]

Hi,
Requested Previously = Backend value?

[adish]

Blue colour : created by flow

Backend value = "requested previously"

Black colour : manually created field

Backend value = "Requested Previously"

[adish]

An update on this: 

It works if i simply change the manually created field value to ''requested previously'' so that it matches with the choice value created by flow (all letters in lowercase). However, i do not think its the best approach as there are many scripts in place that are using the existing value ''Requested Previously'' (first letter capital). So, please let me know if you have any alternate options? or suggestions? Can we write a script in flow to map these 2 choice values?

[adish]

This Question is also regarding the same issue - however i am not able to open the KB article. 

https://www.servicenow.com/community/developer-forum/set-value-of-choice-field-in-flow-designer/m-p/...

[ricker]

adish,

As everyone has pointed out your Flow is setting the value to an incorrect value.  It could be an inactive value with the same display value as the one in black but the value is incorrect.  You need to fix your Flow so it sets the correct backend value (probably "requested previously").  Your Flow is probably setting the value as "Requested Previously" (yes it is case sensitive) and using it as the display value.  You also need to fix all the records with the incorrect value.