Apex Code Development You need to sign in to do that
Don't have an account?
LloydSilver Visual Flow - Problem passing value from dynamic choice
I have a Screen component with one Radio Button field. That field has two choices:
1. Create_New_Contract which is a simple choice field used in a later decision; and
2. Available_Contracts which is a dynamic choice
The Available_Contracts choice displays records from a custom object with a simple filter.
The Choice Label is the name of the custom object record. The Choice Stored Value is the Id of the custom object record.
After the user selects a record from the Available_Contracts they move further in the flow. There is a step where I want to use the (choice stored) value from Available_Contracts. To use it, I'm simply selecting Available_Contracts in the Dynamic Choice section of a formula.
However, nothing is stored there. I used a screen to display the value from that field and it's blank. Now, I can assign the ID obtained after the user selects the record to a new variable, and that works fine. But shouldn't using just Available_Contracts produce the ID of the record since that was what I used for Choice Stored Value.
Bottom line is it doesn't seem like Choice Stored Value is working. At least I cannot use it later in the flow.
Thanks.
Are you relatively familiar with Flows? I ask because I am very familiar with them and over the past week we have hit what we think is a bug with the Dynamic Choices and it's causing a mess in our managed package.
What you describe is exactly how it should work. Our dynamic choice, which worked before Summer 13 release, now returns null when it should not. So if you think you have it built correctly then can you:
1. Log a case with support.
2. (Most important) - In top right corner of Flow designer you can leave feedback. Open that up and put the issue in there. This goes right to Raja who is the Flow lead. I communicated with him yesterday about this Dynamic Choice issue and he was going to look at today, but would certainly be helpful if others let him know they might be experiencing it to.
For us, we have a Dynamic lookup to Contact that returns null and it's not related to security, visibility, etc.
I'm pretty familiar with flows and have built some fairly complicated ones. And they worked. That's what confused me. All of a sudden the dynamic choice values were Null and the flow wouldn't work correctly.
I've provided feedback. I can't submit a case because it's in a developer's sandbox and it wouldn't allow me.
Hopefully they'll get this fixed as the alternative is many hours of retooling several flows, and a very unhappy customer.
In other words, If you have a screen choice field called "Select_Account" and have a dynamic choice called "Fetch_Account", always refer to the "Select_Account" merge field to get the value of the users selection and NOT the dynamic choice.
Hope this helps.
In our case no this won't help because the user isnt' able to make a choice at all. It's that portion that is coming up null. The Dynamic Choice itself, which should have values, is null.
Do you have a time frame for the fix? I have a flow that would require hours of editing to get it to work properly. I can hold off for a little time if the fix is going to be forthcoming.
Any update on timeframe for this fix?
Darrell's issue is something I am aware of. I am not sure if you are having the same issue or not. What error do you see?
"We are working on a fix where referencing the dynamic choice field directly is not getting the value properly."
That's my issue. I cannot reference the dynamic choice field elsewhere in the flow. I used to be able to, but not any longer.
Lloyd's issue sounds different than mine. We can't get the Dynamic Flow to work at all so can't get to the step where we'd pass it somewhere else.
Initially I was not sure if they were related or not, but ours appears related to packaging vs. Flow (evidently they are different processes according to Support).
Darrell
Still looking for an answer as to the timeframe.
Are you guys going to fix this soon, or are you going to force me to spend hours modifying my flow to get around the bug introduced in the last update?
I appreciate the response, although the answer is quite disappointing. This is going to require us to re-tool several flows to overcome this bug. Is there not a quicker way to roll out a fix - through a critical update?