#happy2022workday day-051
Happy 2022 day-051! Today’s update…
Let’s learn about something called the Workday ID (WID) by returning to the topic of the “Self referencing instance” of a Business Object (BO). In particularly let’s look at the Primary BO (PBO) of a custom report.
Please follow along in the worth-1000-words picture:
- Search for what you hope will be the “Self referencing instance” field of your PBO (pic shows the “Worker” field on the Worker PBO)
- If you are not unlucky, you will see the “Self referencing instance” field appear first. If you are unlucky, others have created hundreds or even thousands of calc fields using the BO name in the CF name. This creates a problem. We will return to this problem in a future post, because even if you are not unlucky the trick might still come in handy. If you are unlucky you might not find the “Worker” field on the Worker BO because you hit the #Workday limit of fields when you are searching for “worker”
- Assuming you can find the Worker field on the Worker BO, note the Field Type is “Self referencing instance”
- Click the Actions and click on Integration IDs
- Note the Workday ID on the “Integration IDs” page
- Copy the long WID value into your computer’s clipboard (pic shows I grayed out most of it)
- When searching for the Worker field on the Worker BO try instead entering “wid:” followed by the WID value you copied to the clipboard in previous step (6), and press the Enter key on your keyboard
- The Worker field on the Worker BO appears
Does this help more than 10% of you, those who are not part of the unlucky 10%?
If you are unlucky, step (2) did not show you the Worker field on the Worker BO, so you might need more help to get to step (6).
If you are lucky, you might not ever need to use this “WID in the Search” trick, but I’m guessing some sharing fans might comment here with places outside of reporting where it was helpful to know a WID value.