MultiAutoComplete doesnt retain the selected value

Posted by: muhammad.f.mehboob on 11 November 2019, 3:32 am EST

    • Post Options:
    • Link

    Posted 11 November 2019, 3:32 am EST

    Hi Team,

    I am trying to implement MultiAutoComplete for one of my project using Wijmo. When I select a value from the auto complete dropdown, it gets selected. However, when I select a second value from the dropdown, instead of keeping both first and second value it overrides the first value with the second value. No matter how many values I select from multi auto complete dropdown, it only gets the last value selected. All the previous values gets overridden

    I am using Angular 4 and Wijmo-5.20191.603-rc. Here is my code.

    <wj-multi-auto-complete #employees

    [itemsSource]=“items”

    [displayMemberPath]=“‘fullName’”

    [selectedMemberPath]=“‘uidkey’”

    [placeholder]=“‘Timewriters’”

    style=“height:90px”

    [(ngModel)]=“selectedEmployees”>

    public items;

    public selectedEmployees: any = ;

    map_employees(apiPath)

    {

        this.m_dbService.get(apiPath)
        .subscribe
        (
            data => 
            {
                this.items=data;
    
            },
            errorCode => 
            {
                console.log('errorCode:  ' + errorCode);
            }
        );
    }
    
  • Posted 12 November 2019, 7:08 pm EST

    Hi,

    Could you please try creating a CollectionView object from the data source instead of assigning the data directly:

    import * as wjcCore from '@grapecity/wijmo';
    this.items = new wjcCore.CollectionView(data);
    

    Let me know if this solves your issue or otherwise.

    Regards,

    Ashwin

  • Posted 12 November 2019, 7:24 pm EST

    Hi again,

    The issue was recognized as a bug. We have forwarded a bug report with internal tracking id 406341 to the dev team. We will update you as soon as this issue is fixed. In the meantime, you can use the provided workaround earlier in your application.

    ~regards

  • Posted 26 November 2019, 4:09 pm EST

    Hi,

    The issue has been fixed in the latest nightly build. You can verify the same using the sample below:

    https://stackblitz.com/edit/js-okf3on

    PS: Nightly builds are not suitable for the production environment.

    ~regards

  • Posted 30 April 2020, 4:05 pm EST

    Hi Team,

    I have updated my wijmo version to 5.20201.664 and have started receiving the same error again. Please share your feedback.

    Thanks

  • Posted 3 May 2020, 3:42 pm EST

    Hi,

    We are sorry but we were unable to replicate the issue in the version provided. Please refer to the sample link below that we used to replicate the issue:

    https://stackblitz.com/edit/js-25ht36

    Can you let us know whether we are missing something in order to replicate the issue?

    ~regards

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels