- Home
- Forum
- Angular - EJ 2
- ClearAll icon is not working second time when programmatically assign value
ClearAll icon is not working second time when programmatically assign value
Hi Syncfusion Team,
When I am programmatically assigning value like this:
this.multiselect.value = ['value']
ClearAll button seems that it is not working second time.
Please see short video:
https://im4.ezgif.com/tmp/ezgif-4-897d288651d5.gif
ClearAll button seems that it is not working second time.
Please see short video:
https://im4.ezgif.com/tmp/ezgif-4-897d288651d5.gif
SIGN IN To post a reply.
7 Replies
1 reply marked as answer
PM
Ponmani Murugaiyan
Syncfusion Team
May 27, 2021 10:42 AM UTC
Hi Boris,
Thanks for contacting Syncfusion support.
The provided gif does not open in our end, so we have prepared sample and assigned the value dynamically in a button click and ensured based on your provided information. Unfortunately, we were unable to replicate the issue. If you are using the Drodpown package's lowest version. Please upgrade and verify whether or not the reported issue has been resolved at your end. Kindly check the attached sample and share the below requested details.
Also, we would like to know you that, programmatically assigning value using value property, you have to assign the value mapped in the value field. Here in the below example value field is mapped with Id and so the respective Id ‘Game3’ is assigned to value property, it will update the corresponding text in the component.
|
public sportsData: Object[] = [
{ Id: 'Game1', Game: 'American Football' },
{ Id: 'Game2', Game: 'Badminton' },
{ Id: 'Game3', Game: 'Basketball' },
{ Id: 'Game4', Game: 'Cricket' },
{ Id: 'Game5', Game: 'Football' },
];
// maps the appropriate column to fields property
public fields: Object = { text: 'Game', value: 'Id' };
clickMe() {
this.multiObj.value = ['Game3'];
}
|
- Share Dropdown package version used in your application.
- Share video demonstration with replication procedure.
- Specify which mode is used in the Multiselect component.
- Share the control rendering code snippet.
- If possible try to replicate in the below attached sample.
The above requested details will help us to check and provide you the solution at earliest.
Regards,
Ponmani M
Marked as answer
BJ
Boris Jovicic
May 28, 2021 08:22 AM UTC
Hi Syncfusion team,
Thanks for your replay. I manage to replicate the issue in the example you provide me. It works for the first time. But not for the second.
Steps to reproduce: Click on Apply button. Golf is selected. Click on x icon to clear all on the right side. Works normally. Click Apply button again. Golf is selected. Click on x icon to clear all on the right side. It does not work.
It could be that issue is with [allowFiltering]='true'
As soon as I remove this works normally. But I need this functionality.
Best regards
Best regards
PM
Ponmani Murugaiyan
Syncfusion Team
May 31, 2021 12:14 PM UTC
Hi Boris,
Thanks for providing the issue replicating sample. Currently we are validating the reported issue. We will update further details in 2 business days (June 02, 2021). We appreciate your patience until then.
Regards,
Ponmani M
PM
Ponmani Murugaiyan
Syncfusion Team
June 1, 2021 08:49 AM UTC
Hi Bart,
Thanks for your patience.
We have considered the reported issue “ClearAll icon is not working from second time when programmatically assign value” as a bug in our end and the fix will be included in one of the upcoming patch release which is expected to be rolled out on June 15, 2021. You can track the status using the below feedback link.
We appreciate your patience until then.
Regards,
Ponmani M
BJ
Boris Jovicic
June 7, 2021 07:52 AM UTC
Hi Ponmani,
Thanks for your response. Than, until next release.
Best regards
PM
Ponmani Murugaiyan
Syncfusion Team
June 8, 2021 04:24 AM UTC
Hi Boris,
Thanks for the update. We will let you know once the fix has been included for the reported issue.
We appreciate your patience until then.
Regards,
Ponmani M
PM
Ponmani Murugaiyan
Syncfusion Team
June 15, 2021 12:01 PM UTC
Hi Boris,
Sorry for the inconvenience caused.
We are facing complexity in resolving the reported issue in our end. We will include the fix in Volume 2, 2021 release, which is expected to be rolled out on end of June 2021. We appreciate your patience until then.
Regards,
Ponmani M
SIGN IN To post a reply.
- 7 Replies
- 2 Participants
- Marked answer
-
BJ Boris Jovicic
- May 26, 2021 09:28 PM UTC
- Jun 15, 2021 12:01 PM UTC