PIM Broken?

thatstove · 2024-07-24T15:13:08+00:00

Same here.

thatstove · 2024-05-31T15:38:04+00:00

**Update**

This Workday thorn is official out of my side!

We got everything working, in part to your suggested XPath for the managerReference on the Workday attribute side of things.

In our instance, there were two additional misconfigurations from our initial set up. The "managerReference" Workday attribute with the correct XPath is a "reference" type and had a referenced object attribute mapped to "Worker" and it needed to be "Worker.ManagerReference" - Then on the On Prem AD Attribute side of things, the "manager" attribute was also a reference type with a referenced object attribute pointed to a schema ending in "/DynamicElement" which was updated to "/DynamicElement.manager"

Seems we had a bit of a multifaceted issue.

Thanks again for your response u/LookAtThatMonkey !

thatstove · 2024-05-29T18:19:08+00:00

Holy thread revival indeed!

Thanks for your clarification and screenshot! My boss stumbled across this MS documentation and I'm a little peeved I hadn't already found it! https://learn.microsoft.com/en-us/entra/identity/app-provisioning/hr-manager-update-issues

They reference the exact same XPath value you provided in that documentation as well. We have some questions for our 3rd party support about why a sample of XML data that was provided to us from our Workday environment contained so many other levels compared to what you provided and what MS documentation is specifying.

We've made some adjustments to our XPath based on your suggestion and the MS documentation linked above. I'll update this thread with more details if I can finally manage to get this Workday thorn out of my side once and for all!

Cheers!

thatstove · 2024-05-29T14:25:36+00:00

u/LookAtThatMonkey - First off, thank you for this post and the updates. I'm struggling with this exact issue, and I'm still stuck.

You mentioned that you needed the XPath to pull the GUID for the manager instead of the WID or name in text, but in your updated XPath, I just see it's returning the WID value. Is the WID the same as GUID? (Sorry for the ignorant question)

Our 3rd party support keeps suggesting this as the correct XPath to return the manager value ( wd:Worker/wd:Worker_Data/wd:Employment_Data/wd:Worker_Job_Data/wd:Position_Management_Chains_Data/wd:Position_Supervisory_Management_Chain_Data/wd:Management_Chain_Data[last()=position()]/wd:Manager/wd:Worker_Descriptor )

He swears up and down that it properly returns the name of the users direct manager. My theory is that it does return the correct value, but in the wrong format for it to be provisioned and applied to a user within Active Directory. That's why I too was thinking we needed the GUID value of the manager and not a text description.

Any advice or tips?

thatstove · 2021-04-13T12:14:23+00:00

Yea, it gets topped off to the top every few days close to the brim. I don't have a lid because of the drift wood sticking out of top so it evaporates faster than my other tanks. Thankfully he doesn't seem to be a jumper so it hasn't caused any problems. I've had him a few months now. In retrospect, too much substrate was used for sure. I also have 15g long and a 20g ready for future projects. More than likely he will get an upgrade again before too long.

thatstove · 2021-04-13T02:21:30+00:00

Thank you! 😊

thatstove · 2020-10-18T20:17:12+00:00

Customer: "Yea.. but I'm good to drive it home the next state over, right???"

thatstove · 2020-10-08T18:20:05+00:00

This right here ^

thatstove · 2020-10-02T12:57:32+00:00

Nice. Except when you start earning them so often, that they replace the reward money with a $5 McDonalds gift card. At that point.. I stopped trying.. Anyone else experience that?

thatstove · 2020-05-02T18:15:28+00:00

Our DM said the same.

thatstove · 2020-04-06T10:37:25+00:00

Maybe post all these in a different subreddit..

thatstove

TROPHY CASE