Filter users by ID in query form
I often get client requests to analyze specific group of employees selected only by their emails. The selection doesn't map to any combination of org dimensions, so it is not possible to select them using regular filters. It would be much helpful, if we could have a query filter based on a series of string values. It could work like the SQL's filtering: WHERE EmployeeId IN ("ABC","DEF","GHI") For my current case I need to select 450 employees from a list. Firstly, I query the whole 7k population and then choose my focus group. Not very efficient method, my initial queries are just unnecessarily big.Static dates in the report generation
I think an idea to improve that recently a client share with me was about the custom dates when they generate a report, and let me explain more about it because sounds very interesting. In this case she wants to identify trends in the organization, and want to have the info updated to the last week, but that the starting week stays statics. She wants to instead of keep watching the results of a year, could be: 1 year + 1 week, 1 year+ 2 weeks, etc, the only way she can do this its by creating each week a new report with the dates, but might be a gool idea to have some autoupdate split. RegardsTracking save events for Office documents
How can we get the autosave or save events by person? We need this feed in order to expand the current Insights data from collaboration signals only to include solitary work by individuals. eg. if an individual works into the night on a PowerPoint presentation their workweek span should include that time, but it is not collaboration time from their calendar so it is omitted.VIVA Insights Query Results - Rerun Feature / Robust Address for Query
Today, VIVA insights only allows two options for queries either auto-refresh (that has to be renewed) or one-time only query. The auto-refresh is great but it only gives 1 years worth of data instead of all data, and the one-time only query can only be run once without creating an entirely new query with a new "ID". Preference for VIVA Insights to offer up the ability to extend the auto refresh beyond 1 year to include all data in the client for use with a Azure data lake or database. Unfortunately with only a years worth of data, then I have to have a one time only query to get all the data to a data and then use another query to auto-refresh to append the new data --- and then this gets overly complicated when you have new licenses being added or removed throughout the year Preference for VIVA insights also offer up the ability to re-run a one time only query that keeps the exact same ODATA feed link. This static address would allow on-demand refreshes instead of hitting the Microsoft server every week and allows the creation of PowerBI models that are better connected to the data. This re-run essentially would just be an option (can't change fields or any details about the query)...you just rerun with the exact same settings -- therefore if it had last one year then it would rerun again with new dates with last 1 year.Meeting query: hybrid options
My customer wants to track if the return to worksite process is leaving the remote workers out of the communications loop. One way to avoid that is offering double presence options for meeting participants by the organizer: physical room and Teams link. We can check the meeting Resources column to know if a meeting has the physical space component but there is no way to check if there was a Teams link (or any other video call link) attached. A related boolean column in the Meeting Custom Query would resolve this problem.Working Hour Customization by the Day
We have employees that want the ability to indicate part time as well as difference in working hours from typical 8 to 5 job. Is there a way to have outlook provide option that you can both select the days of the week as well as the hours for each day selected? Idea here would be a Gen Z who wants to work from 9 to 7 on Monday, 8 to 6 on Tuesday, 12 - 10 on Wednesday and Thursday, and then work 8 - 12 on Friday. Same work week but extremely different work pattern than Outlook would allow. I sense that there are many other companies in same boat who want to offer flexibility and allow us to have that show up in our available time in Outlook so our colleagues can see and then respect the decision so that meetings are scheduled in times that work for all.Tentative Accept - Separate Field in Meeting Query
One of our analysts discovered that when we run a meeting query that we do not currently have the ability to separate tentatively accept from accept as a selectable field. This caused quite a bit confusion when we started using the the attendee exclusion here at CMI. We would like to be able to get a separate field for each meeting that calls out "accept", "tentative", "decline", and "no response" so we can quickly see how attendees is calculated. At CMI, accept and tentative are no where near the same thing but find that we actually put both in the same bucket as "accept"Fragmented / Working Hours - Query Designer
I would like to recommend the addition of fragmented hours (and working hours) to the query designer as a selectable metric like focus hours. I know that fragmented hours is located in the explore area and is pseudo-calculated in PBI templates. However, I would like to see the actual measured value for each person be able to be extracted and reported on. It is not reliable to use workday span and subtract meeting hours and focus hours to calculate fragmented hours. Therefore it would be great to get one or both of fragmented hours and or working hours so we can back calculate the other. My definition of fragmented hours would be less than 2 hours not in meetings during working hours to make it similar to focus hours. It would also be great to keep the similarities with focus hours and add an uninterrupted fragmented hours option as well in which a collaboration activity was not done during this time period.