Lag when doing on change with Multipicker #11640
Answered
by
andz-bb
vaishnaray
asked this question in
Help
-
Beta Was this translation helpful? Give feedback.
Answered by
andz-bb
Sep 1, 2023
Replies: 3 comments
-
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
melohagan
-
Thank you so much! Will try this.
…On Fri, Sep 1, 2023, 5:24 AM Andrew Thompson ***@***.***> wrote:
hey Vaish,
in this case you need to use the {{ Field Value }} binding for the value
instead of the field on the form binding. At the point when the on change
action is being run the form object will still have the old value while the {{
Field Value }} binding has the newly changed value. You'll be able to
find it on the bindings sidebar under the name of the field component, in
your case Multiselect.
[image: image]
<https://user-images.githubusercontent.com/110921612/264995034-bff969cd-aef1-41ea-a720-10fea61bb071.png>
hope this helps - if you have any questions on this feel free to reach out
Andrew
—
Reply to this email directly, view it on GitHub
<#11640 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACIEETEE455AHLXJVRYWLJDXYGZURANCNFSM6AAAAAA4GQJL7Y>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
-
I can't see Multiselect - Field Value in the list when I try to do a
Trigger Automation.
[image: image.png]
[image: image.png]
…On Fri, Sep 1, 2023 at 5:24 AM Andrew Thompson ***@***.***> wrote:
hey Vaish,
in this case you need to use the {{ Field Value }} binding for the value
instead of the field on the form binding. At the point when the on change
action is being run the form object will still have the old value while the {{
Field Value }} binding has the newly changed value. You'll be able to
find it on the bindings sidebar under the name of the field component, in
your case Multiselect.
[image: image]
<https://user-images.githubusercontent.com/110921612/264995034-bff969cd-aef1-41ea-a720-10fea61bb071.png>
hope this helps - if you have any questions on this feel free to reach out
Andrew
—
Reply to this email directly, view it on GitHub
<#11640 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACIEETEE455AHLXJVRYWLJDXYGZURANCNFSM6AAAAAA4GQJL7Y>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
hey Vaish,
in this case you need to use the
{{ Field Value }}
binding for the value instead of the field on the form binding. At the point when the on change action is being run the form object will still have the old value while the{{ Field Value }}
binding has the newly changed value. You'll be able to find it on the bindings sidebar under the name of the field component, in your case Multiselect.hope this helps - if you have any questions on this feel free to reach out
Andrew