Unanswered

Workday HCM Connector - InternalServerError

(0) Share

Report

Posted on by CarlDeanCatabay

Hi All,

I'm trying to build an automation to create an onboarding ticket in Solarwinds Service Desk (formerly Samanage) when an employee is added in Workday. Currently, I am doing a manual trigger as we wanted to test if the connector works before we move to automated trigger which is the When an employee is added or updated.

I have the connection set up with the Workday endpoint, username and password provided by our ERP administrator for this integration but when I am testing my flow, it always gives me an InternalServerError and the flow run times out after 10 minutes with two (2) retries:

Capture - Workday.png

I tried the following URL formats:

https://####.workday.com/ccx/service/tenantName
https://####.workday.com/ccx/service/tenantName/Human_Resources
https://####.workday.com/ccx/service/tenantName/Human_Resources/v##.#

As well as the following username format:

<username>
<username>@<tenant>

But none of these worked and I always get the same InternalServerError.

Has anyone else had this issue? How did you resolve it?

This is my first time asking here so please be kind. 🙂

Categories:

Using connectors

All responses (3)

Answers (0)

Sort by

rakadakaka 77 on at

Like
a
(0)

Report
Copy link

Link copied!

@CarlDeanCatabay: We have tried connecting to workday connector from flow and were able to connect successfully , but we did not use the power automate connector as we had to get some other business object data apart from workers and employee and the workday soap operation action had issues .

URL to be used while creating connection : https://<<workday host>>/ccx/service/<<tenantName>>/

Username which we used : username@tenant and respective password .

I would suggest you do connectivity to the workday Human Resource SOAP service via SOAP UI as well to make sure the connectivity is working fine .

You can create the SOAP project in SOAP UI and give it a try by calling simple operation like GetWorkers .

Please note : when you are passing authentication to the Request from SOAP UI , apart from passing username and password , you need to WSS Password type as "Password Text"

Also try doing a test accessing the Workday Human Resource SOAP from the office network as well as from public internet just to eliminate any point related to network restriction issue .

Please let us know , once you are able to execute these steps how it goes .
JustAnotherGuy 2 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @CarlDeanCatabay - check the password you're using. If it does contain special letters such as "&" or similar, you need to have a new integration user (password) provisioned to you, which can be used with the Workday HCM connector (special letters which cannot be used in XML as is will result in such Internal Server Errors, as these will generate malformed XML).
nonodename 2 on at

Like
a
(0)

Report
Copy link

Link copied!

That's a great point. If you can craft the SOAP headers yourself, you can get around this using a CDATA section. e.g. instead of
<wsse:Username>{{Username}}</wsse:Username>
do
<wsse:Username><![CDATA[{{Username}}]]></wsse:Username>