u/Recent-Bicycle6738

Hi everyone! Has anyone here experienced using REST POST/Workday REST API from Workday Studio to update or add values to a Custom Object?
I’m currently working on a project where we’re trying to automate the process of updating/adding values to a Custom Object using Workday Studio.

Use REST POST to update the Custom Object

The Custom Object is non-effective-dated and single-instance

Target is Worker

We’re using the Custom Object API endpoint with updateIfExists=true

The issue I’m encountering is:
✅ If the custom field already has an existing value:
The REST POST successfully updates the value.
❌ If the custom field is currently blank:
The REST POST fails with an error when trying to populate/add the value for the first time.
Has anyone encountered this behavior before?
I’m wondering if the issue is related to:
The updateIfExists behavior

The REST API version being used (V1 vs V2)

The payload structure when the existing value is blank/null

How Workday handles creating the first value in a Custom Object

Whether a different REST method or endpoint is required to add a value versus update an existing value

What could be causing this, and what would be the recommended approach in Workday Studio to populate a previously blank Custom Object field?
Any examples of the correct endpoint/payload structure or guidance would be greatly appreciated. Thanks!

Hi everyone,
I'm working on a Workday requirement where the client wants to create an identifier for workers who are “Privacy Champion”
The goal is simply to have a field or indicator in Workday that identifies whether a worker is a Privacy Champion. The client may also want to use this identifier in an existing custom report.
I'm currently considering creating a custom field on the Worker business object with a Boolean (Yes/No) field type.
However, I'm not entirely sure if this is the most appropriate approach, particularly regarding:
Whether a custom field on Worker is the best solution for this type of designation.

Whether a Custom Object would be more appropriate.

How to make the identifier available for reporting.

What security domain or configuration would be needed.

Whether there is an existing Workday functionality or delivered field that could be used instead.

My questions:
If a client asks you to create a simple identifier to indicate whether a worker is “this” (e.g., Privacy Champion, Mentor, Safety Representative, etc.), what approach would you normally take in Workday?

Would you use a Boolean custom field, Custom Object, or another configuration?

What factors would you consider when deciding where to store this identifier?

Are there any limitations or best practices I should be aware of, especially if the field needs to be used in custom reports?

I'd appreciate any advice or examples from your experience. Thank you!

Hello @everyone

Does changing workshift mapping in an integration affect other payroll integration?

Hello, why does a pgp file failed to convert to G2?

Hi everyone

Asking if how are we gonna override the ouput of an end date in Payroll input earnings and deduction? They want the end date to be EOM.