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
51 stars 2 forks source link

Lookup by Department #44

Open Worrelpa opened 1 year ago

Worrelpa commented 1 year ago

I had a request to enable people to lookup by department.

From research and experimentation I found the APIs for Office365 users were limited to a set number of return records and criteria as some of the calls don't return the department field. A lack of consistency Microsoft's side on that. Also MSGraph API calls were a bit complex.

All I could do was extract the data put it into a table and then update it with a cloud flow once a week to get new people added, account for department moves and remove disabled accouns. (I still have to build that flow). For now I just used a dataflow to import a manually imported extract from AAD from an excel file to use as a lookup. It works but not the most efficient way of doing it.

I see the notifications table keeps the department field, but because not everyone in AAD has a record for lookup so people are missing.

Any suggestions on a better way to do this? I want to run a flow from the app if possible.

stuartridout commented 1 year ago

Let me ponder on that (I’m away on holiday currently).  The notification records table has the list of users and includes department so we can list them by department on the View By Site page without doing lots of Office365Users calls which can be quite lengthy.  StuartOn 26 Oct 2022, at 13:25, Worrelpa @.***> wrote: I had a request to enable people to lookup by department. From research and experimentation I found the APIs for Office365 users were limited to a set number of return records and criteria as some of the calls don't return the department field. A lack of consistency Microsoft's side on that. Also MSGraph API calls were a bit complex. All I could do was extract the data put it into a table and then update it with a cloud flow once a week to get new people added, account for department moves and remove disabled accouns. (I still have to build that flow). For now I just used a dataflow to import a manually imported extract from AAD from an excel file to use as a lookup. It works but not the most efficient way of doing it. I see the notifications table keeps the department field, but because not everyone in AAD has a record for lookup so people are missing. Any suggestions on a better way to do this? I want to run a flow from the app if possible.

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