Create Position Fails: Custom Organization Type Required for Position Assignment
What it means
A tenant's Position Organization Assignment configuration can mark one or more custom organization types as required whenever a position is created or edited. If the Create_Position SOAP request, whether called directly or through an EIB that wraps it, doesn't include an organization reference for at least one of those required custom types, Workday rejects the request even though every other field is valid.
Troubleshooting
- Read the fault's Detail_Message closely, it names the restricting element (Custom_Organization_Assignment_Data under Position Organization Assignment Data) and confirms this is a configuration requirement, not a malformed request.
- In the tenant, review the Position Organization Assignment business process configuration to see which custom organization types are marked required for position creation.
- Check the source data or mapping feeding the integration to confirm whether an organization value for that custom type exists for the position being created, it may simply be missing from the source system.
- Add the required custom organization reference to the Create_Position request payload, or the underlying EIB source data, for the missing type.
Add a valid reference for the required custom organization type to the failing request and resubmit.
Update the integration's field mapping so every required custom organization type configured in Position Organization Assignment is always populated from source data, and add a pre-submission validation step that flags positions missing a required custom org before the SOAP call is made.