stuartridout / teamlink

TeamLink is a free Microsoft Teams Power App using Dataverse for Teams. It is a space where your team can share there whereabouts for the week ahead directly in Microsoft Teams. Users can select who they want to 'follow' and see the upcoming presences of or can view by site to see who is planning to be on site on that day. TeamLink allows you then to message to see if the person wants to meet up for a coffee ... all from the click of a button!
MIT License
50 stars 2 forks source link

Duplicate presence records #43

Closed Worrelpa closed 1 year ago

Worrelpa commented 2 years ago

Not sure if anyone has seen an issue where presence is when changed is logging 3 presence records which is knocking off the confirmed number in the site view. As it is counting the rows and getting more than people showing up in the onsite view.

Going to try to work around it by filtering the count on unique records by email for each user mail id. Though I am not sure how to pick up the latest record for the count to be correct.

stuartridout commented 2 years ago

What version of the app are you on?On 26 Oct 2022, at 13:16, Worrelpa @.***> wrote: Not sure if anyone has seen an issue where presence is when changed is logging 3 presence records which is knocking off the confirmed number in the site view. As it is counting the rows and getting more than people showing up in the onsite view. Going to try to work around it by filtering the count on unique records by email for each user mail id. Though I am not sure how to pick up the latest record for the count to be correct.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

Worrelpa commented 2 years ago

Latest 10038

We have modified our instance some what but not that part of it. We added / hid a few options but not changed the core of it.

I am wondering if someone is clicking multiple times on the icon before the first patch has gone through. So it creates new records each time. Thinking of trying a disable the part and then enable once the processing is done to avoid that, but that ony a guess at what is happening. Also will look at getting distinct records for the site count.

stuartridout commented 1 year ago

I think that is most likely what's happening. Or potentially where there is a slow connection.

I'll add this to the backlog for bug fixes.