Workday Ad Hoc Bank Transactions

[dkunzler]

Hello. I was wondering if anyone has used the Workday connectors for creating Ad Hoc Bank Transactions. Especially for a payroll journal entry. 

I currently am using the Workday Webservices connector and I have it creating the Ad Hoc Bank Transaction, however, there are some fields for the line items I create that do not seem to be available through the connector, yet are required fields for the transaction inside of Workday. Wondering is someone has come across that and what you may have done to get around it.

I do see that the connector can create the transaction using XML as well. So I may give that a shot and generate an XML file for it in order to try and get the missing info into it.

We do have an EIB I could upload to as well. However, the template from Workday for that is an xlsx file and in order for me to automate filling that out I would need a Microsoft OneDrive account and we are all on Google Services. Unless someone has a hack for being able to create an XLS file from Google Sheets that route may not be helpful. 

Thanks!

[ndy]

Dear @dkunzler 
It sounds like you are facing challenges with creating an Ad Hoc Bank Transaction in Workday due to missing fields that are required for the transaction. Here are some strategies that could help address your concerns:
1. XML-based Ad Hoc Bank Transactions via Workday Webservices Connector
Since you mentioned that some fields aren’t exposed through the Workday Webservices connector, you can try creating the transaction using XML Tools by Workato, which could give you greater flexibility in filling in all the required fields.
Steps:
 - Refer to the Workday XML schema for Ad Hoc Bank Transactions to understand the structure and fields.
 - Create a custom action in Workato to send the XML payload to Workday. The Workday Webservices connector supports      custom requests, so you can manually structure the XML for submission.
- Test the XML payload to ensure all the necessary fields are included and Workday accepts the transaction.
2. Use a Custom Python Script for XLSX Conversion
This approach has limitations that are dealing with Excel files, the file's size is no larger than 5MB when used with the Pandas library due to temporary storage required by Pandas and Excel being a compressed form of data which is uncompressed when used with Pandas.

[sidjayawardena · Accepted solution]

I just ran into a similar problem on the revenue connector because I didn't see the fields initially

However the Workato product manager for Workday Integrations showed me you can check the optional fields, the fields with attributes section and the fields with multiple values section to get what I needed

I'm more of a Workday integration expert than a Workato one but if you reply with a list of fields, I will try to see what is missing and where you might be able to find them

Also