Autocomplete default value doesn't reflect the updated value
We have an Autocomplete reading from a Report Definition that displays two values: ‘Label’ and its corresponding ID.
When we modify the label of the parent, the report definition successfully returns the updated label with its corresponding ID However, the Autocomplete stills shows the old value of the label (before the renaming) as the default value When we scroll down to see the list of labels and their IDs, that old value shown as the default value in the autocomplete is not in the list of the report definition.
1) Create a report definition that returns two values: ID and its corresponding Label 2) Rename the Label that must be displayed by the report definition (and that is the initial selected one in the Autocomplete) 3) Check the Autocomplete's default value: it will be the old label (before the renaming
Any ideas on how to set the default value of the Autocomplete to the updated value ?
Thank you in advance,
***Updated by moderator: Lochan to add Categories***
I don't understand where the autocomplete is actually used. Is it the control that's displaying the "Label" in the first column of the grid? Are you ever refreshing the Tree Grid after submitting the modal (do you have the "Allow refresh on update" option selected under Grid Operations)? What edit-mode does the tree-grid use (it looks like it's master-detail with a modal dialog - but if that's the case, why use an autocomplete in the first column and not just a label control)? Have you tried configuring a row refresh condition on the tree grid for when the label is updated?
If none of this works, could you provide a rules trace of this scenario?
1) The autocomplete that is actually used is "Parent". The "Label" control in the first column of the grid represents the "Parent" field in the "Create - Edit Module Details" section as you see in the below screenshot.
2) Are you ever refreshing the Tree Grid after submitting the modal (do you have the "Allow refresh on update" option selected under Grid Operations)? Answer: Yes
3) What edit-mode does the tree-grid use (it looks like it's master-detail with a modal dialog - but if that's the case, why use an autocomplete in the first column and not just a label control)? Answer: Because the user is allowed to change the Parent field
4) Have you tried configuring a row refresh condition on the tree grid for when the label is updated? Answer: Yes
5)Since none of this worked, I am attaching a rules trace of this scenario.
I had my Support Engineers take a look at this and they believe that this may in fact be a product defect and would like to conduct additional troubleshooting with you. Could you go ahead and open an SR and reference this PSC post in the details. Then once opened, please reply here with your SR # so that we may link the two for easier troubleshooting.
I opened an SR (SR-A88684) for this issue since mid July 2016, we had many screen sharing sessions.
They eventuelly said that by default, we are getting the value in the autocomplete list. But to get the value populated directly on the label, we need to perform some activity or data transform and that autocomplete is working fine from design point of view.
They suggested to raise this issue on the product support community as that this was beyong the scope of GCS.
I have re-opened the SR and will keep you updated if the issue got solved.
For future reference, it would have been more productive if you had referenced that SR in your original post, as well as framing this post as a question about how to implement the requirement – not as if you were reporting a new defect.
I'll review the SR and see if I can a better idea of what exactly is necessary from its notes.
I've looked into this and it seems that the SR you reopened was rejected, though I believe this may have been premature - I've asked that this be looked into.
In the meantime, set up a very basic example in UI Gallery and in my case, it's working. One thing I'm confused about is the set up of your Autocomplete. If you're results are coming from "Label" and you're storing that in "ParentName" - when are you ever actually updating "Label" ?
Many many thanks for your involvement in the issue :)
After further trials, we managed to solve the issue !!
We added an activity "UpdateParentModuleLabel" on pre-processing of the flow action (that references the 'Create-Edit Module Details' section). It fetches the renamed/updated value of the parent and stores it in the property 'ParentName'.