|
| 1 | + |
| 2 | +Getting PnP Modern Search to show work anniversaries should be easy enoght, right? Just add a couple of managed properties and a couple of web parts and you are done. Well, not quite. |
| 3 | + |
| 4 | +The problem is that date manipulation in KQL is hard at best and sometimes impossible. In order to find a work anniversary you must compare Today and the Hiredate managed property, but ONLY the day and month part. |
| 5 | + |
| 6 | +Calculating how many years the employee has been with the company is also required and it seems like there is no way to get that using KQL. |
| 7 | + |
| 8 | + |
| 9 | + |
| 10 | +## Objective |
| 11 | + |
| 12 | +We want to be able to display two options: |
| 13 | +- Employees having a work anniversary today, and also how many years they have been with the company |
| 14 | +- Employees having a work anniversary within the next 7 days + number of years. |
| 15 | + |
| 16 | +## How to cheat |
| 17 | +In order to achieve the objectives, I had to get: |
| 18 | +- The account |
| 19 | +- The hiredate, but with the year segment being the current year |
| 20 | +- The number of years the employee has been with company at the next anniversary |
| 21 | + |
| 22 | + |
| 23 | + |
| 24 | +Lets add birthdayThisYear while I was at it, in order to be able to show upcoming birthdays. |
| 25 | + |
| 26 | + |
| 27 | +The basic idea is that we want to change the hiredate from eg. 10/26/2005 to 10/26/2023 as that allows us to compare Today with this value 😀 |
| 28 | +(RefinableDate12 is mapped to the HiredateThisYear property) |
| 29 | + |
| 30 | +Who is having a work anniversary today? |
| 31 | + |
| 32 | + *RefinableDate12=Today* |
| 33 | + |
| 34 | +Anniversary within the next x days is also a piece of cake: |
| 35 | + |
| 36 | + *RefinableDate12<{Today+7} AND RefinableDate12>{Today}* |
| 37 | + |
| 38 | +## Implementation |
| 39 | +Asking the intern to keep the list above in sync would be a cruel and unusual punishment, and hence actually forbidden in the USA, something to do with a constitution or something like that. |
| 40 | + |
| 41 | +The list should of course be synced with the source, in this case the User Profile Application, at least once each month. The reason I am not using Graph is that birthday is not in the schema. |
| 42 | + |
| 43 | + |
| 44 | + |
| 45 | +**Prereq: Map SPS-Birthday and SPS-Hiredate to RefinableDate00/01 or similar** |
| 46 | + |
| 47 | +Once data is showing up in those RefinableDate properties you should be ready to create the list. |
| 48 | +Grab the script here . It will create a few Site Columns and a Content type on the site collection of your choosing. The list is then created, and the Content type added to the list. |
| 49 | +The Add-UserDataToList function will query the UPA for accounts and write the data we need to the list. |
| 50 | + |
| 51 | +Hit the Reindex site in the site collections Search and Offline Availability section for the site columns to be picked up by search. |
| 52 | + |
| 53 | +Map the crawled properties to a couple of RefinableDates. If possible it is recommended to make this mapping on the tenant level as it ensures that you can use them in your entire tenant. |
| 54 | + |
| 55 | +Find the Content Type ID of the Content type created by the script. |
| 56 | + |
| 57 | + |
| 58 | +Add a Results web part, name it "Todays work anniversaries" |
| 59 | + |
| 60 | +Set the Query template to: |
| 61 | + |
| 62 | +*Contenttypeid:0x01009290F0FA40E7CB42B55D6D96F897262B\* RefinableDate12=Today* |
| 63 | + |
| 64 | +*(replace 0x01009290F0FA40E7CB42B55D6D96F897262B with the value for the your content type)* |
| 65 | + |
| 66 | +Add a Results web part, name it "Upcoming anniversaries (7 days)" |
| 67 | + |
| 68 | +Set the Query template to: |
| 69 | + |
| 70 | +*Contenttypeid:0x01009290F0FA40E7CB42B55D6D96F897262B\* RefinableDate12<{Today+7} AND RefinableDate12>{Today}* |
| 71 | + |
| 72 | +*(replace 0x01009290F0FA40E7CB42B55D6D96F897262B with the value for your content type)* |
| 73 | + |
| 74 | + |
| 75 | + |
| 76 | +Add the managed properties birthdayhiredateAccountOWSUSER, nextWorkAnniversaryInYearsOWSTNMBR, RefinableDate10, RefinableDate12 to the Selected Properties in both web parts. |
| 77 | + |
| 78 | +Enter Layout slots |
| 79 | + |
| 80 | +Change UserEmail to use the birthdayhiredateAccountOWSUSER property |
| 81 | + |
| 82 | +Change Date from Created to RefinableDate12 |
| 83 | + |
| 84 | +For both web parts you can select the People layout on "page 2" in the web part configuration. |
| 85 | + |
| 86 | +Set Secondary text to: |
| 87 | + |
| 88 | +{{{Title}}} has been with us {{{nextWorkAnniversaryInYearsOWSTNMBR}}} years |
| 89 | + |
| 90 | +(remember to click Use Handlebars expression) |
| 91 | + |
| 92 | +Set Tertiary text to: |
| 93 | + |
| 94 | +{{getDate (slot item @root.slots.Date) "MMMM-D"}} |
| 95 | + |
| 96 | +(remember to click Use Handlebars expression) |
| 97 | + |
| 98 | +Set the sorting on the Upcoming Anniversaries to RefinableDate12 asc |
| 99 | + |
| 100 | +Run the Add-UserDataToList function in a runbook or similar once a month and you should be done😊 Near the end of the year you might need to run is once per day. |
| 101 | + |
| 102 | + |
0 commit comments