Forum Discussion

danieleperilli's avatar
danieleperilli
Kudo Commander
8 years ago

SelectionId from data received with fetchMoreData()

I have a problem with the fetchMoreData() function. I'm able to retrieve all the data from my dataset, but when I try to generate the selectionIds, something strange happens.   I use this code to ...
Need Help
Anonymous's avatar
Anonymous
Not applicable
7 years ago

Hi v-viig & danieleperilli 

I have the same issue - was there a work-around for this or a schedule on the fix?

Thanks,

Matt

dm-p's avatar
dm-p
Super User
7 years ago

+1 on this. Have the code fully implemented (was working on API 1.x) but switched off in my current releases as it's not in the same 'shape' when fetched in 2.x. Would be good to know if there's an ETA on a fix :)

  • v-evelk's avatar
    v-evelk
    Microsoft Employee
    7 years ago

    It is expected behavior that SelectionIds are built differently in API 2.x than in API 1.x, however, this mustn't break a visual selection logic.

    To clarify the issue I need to understand what version of API do you use.

    Is it possible to send us .pbix with a case to [email protected] because I couldn't reproduce some troubles with selection and fetchMoreData() function in the last API?

     

    Thanks!

     

    Evgenii Elkin,
    Software Engineer
    Microsoft Power BI Custom Visuals
    [email protected]

  • v-evelk's avatar
    v-evelk
    Microsoft Employee
    7 years ago

    Hi guys,

     

    I am checking the status and will provide details here soon.

     

    Evgenii Elkin,
    Software Engineer
    Microsoft Power BI Custom Visuals
    [email protected]

  • dm-p's avatar
    dm-p
    Super User
    7 years ago

    Hi v-evelk and thanks for having a look. I'll need to bow out to others on the selectionId issue, and I think I might have latched onto a different problem, so apologies to others on this thread.

     

    My issue was more general in that fetchMoreData() hadn't been working since I moved from 1.13 to 2.1 and hadn't seen an update on its resolution. I've migrated my visual to 2.3 and the code works fine now. I'll consider adding the feature back into my next update with a bit more testing.