Microapps

Troubleshoot common errors with the Workday integration template

This article is designed to help you solve issues with your Workday integration.

Approve/Deny PTO microapp

Problem

A green pop-up message is shown, but the PTO status in Workday does not change.

Solution

Make sure that the PTO that you create is in amount 4 or 8 in hours.

Problem

I get an error message when approving a PTO.

Solution

  1. Log into Workday as a manager and check your inbox items to see if the PTO request is still there. If it is not there, it was already approved/denied.
  2. If it is there, use our documentation for Testing Workday API calls and try approving a request via Postman/SoapUI.

Create PTO microapp

Problem

No PTO types are available.

Solution

  1. Check if the email address of your Workspace account is the same as the Primary Work Email on Workday. If not, this is the issue.
  2. Your Custom Report in Workday might have missing or wrongly configured fields. Please compare it with the custom report we provided and check for any differences. These are the custom reports we use: Create custom reports.
  3. The Time off types per plan report path does not want the WSDL url like the other Custom Report URLs. This is because we are using a REST API call here. Check the link above to verify that you are using the correct path.
  4. Verify that the user account has a PTO plans/types within Workday.

Empty fields/No data

Problem

The Workspace blade loads, but there is no data in any of the fields.

Solution

  1. This means the cached database is not being populated. Call an API endpoint related to the data you need to check whether you get a response from Workday with the credentials you use. Perform a Test Workday API call walk-through for every API call. If the API call returns all the data, create a JIRA/ServiceNow issue. If the API call ends in an error or does not return data, there is an issue with your service account.
  2. When creating custom reports in Workday, you can give the report a custom name but the namespace value within the report needs to match what is in the documentation.

Problem

The Workspace blade loads, but there are some unpopulated fields.

Solution

  • This most likely happens because the security group assigned to your service account is missing a security item in Workday. Find all security items your security group needs here: Security group permissions.
  • For an example of a custom report configuration mistake: When defining the columns of the custom report, be sure the Time Off business object is selected and not the Time Off report element. You can tell the difference by whether there’s an icon. Choose the Time Off” that does not have the icon.

Problem

My deep links are not loading Workday.

Solution

Check the integration configuration if you have filled in Instance URL correctly. For more information about how to identify your instance URL: Find your URL. Search for instance URL.

Synchronization

Problem

Synchronization fails within a few seconds/minutes.

Solution

  1. Most likely there is a configuration issue. Edit your integration and look at every field to encounter any possible errors.
  2. Check whether you can log in to Workday with your service account.

Create a Custom Report in Workday

Problem

I can’t find a business object to build my Custom Report.

Solution

When creating a custom report to see All Time Offs in the data source, you need to clear Optimized for Performance to be able to select this Business Object.

Problem

Custom Report name and namespace must match.

Solution

When creating custom reports in Workday, you can give the report a custom name. However, the namespace value within the report needs to match what is in the documentation: Create custom reports.

Troubleshoot common errors with the Workday integration template