Web part name (as shown in web part properties) to which you’re suggesting an enhancement
Anniversaries Web Part, also known as Anniversaries, Milestones and Birthdays Web Part What is current web part behavior (or look) that doesn’t work for you?
In order to configure the anniversaries, it is currently a manual entry into a list one by one, or manual Excel upload for the data to be populated. When attrition is high and you have a lot of employees, a new upload would have to be done at a minimum of weekly, and I can’t invest that amount of time to keep the web part current.
> Have a screenshot (please do not include confidential info in your screenshots)?
None needed, it’s the standard configuration for the web part. What would you like the web part behavior (or look) to be?
An automatic integration with AD or other so that the refreshed and pulled data is always current. As the Directory webpart and others are already able to be integrated with the employee database, hopefully this would be a relatively similar fix.
> Have a sketch or a mockup?
None needed, as its backend integration. What is the scenario for which you need the suggested new look/behavior?
We have decided to use Origami as part of a new Intranet launch with the rebrand of the company. As I’m getting to know parts, I’m offering gentle suggestions or wishes.
Thank you for your suggestion!
We just have a few follow up questions to clarify your needs.
If employee Anniversaries are taken from Azure/Entra ID, that means that only IT (or other admin would be able to update Anniversaries). Will this update still be useful to you?
If the data source for Anniversaries was the same data source as People Directory, would that work for you? People directory takes data from SharePoint User profile (which is synched with Azure/Entra ID).
Entra ID/Azure often holds system accounts, contractor accounts, accounts of inactive users under investigation, resource accounts (printer/scanner accounts, meeting rooms etc) and other user accounts that you would not want to show in Anniversaries. This would require some kind of a filter to hide accounts that you don’t want to show. How do you see managing these exceptions?
Apologies I’m not IT here, so forgive my lack of knowledge.
Doesn’t Azure link and pull data from the HR ERP system, therefore the data would be updated by HR?
In theory it sounds like using the same data source as People Directory would work, we would just need to add a field to Azure that recognizes “Date of Hire”.
We ran into the same problem with the People Directory, and have tried filtering those out since they don’t have a department per say.
What about writing a power automate workflow to edit the list itself that the web part speaks to? (thought from IT)
Looking for ideas and help really, I was just tossing things out. Thanks!