Concept: Custom Fields in Custom Reports and Calculated Fields

You create custom reports with custom fields in a similar way to creating custom reports with other Workday fields. You can create calculated fields based on custom fields.

You can use a custom field in reports:

Workday doesn't index custom fields. Therefore, when you use custom fields to filter or group data on a high-volume business object, the report will run slowly. Example: You have more than 50,000 workers and you use a custom field on a custom object on the Worker business object to filter or group workers, the report could run for several minutes.

When you create a custom field, you select or create categories for the custom field. The default category is

Custom Fields

, but you can assign custom fields to any existing or new category.

To enable users to select a custom list value in the prompt, you can create or predefine filters. In both scenarios, the prompt displays custom list items that are specific to that custom list. Example: You create a custom field called

My Certifications

with a custom list type of Worker Certifications. You also create a filter on

My Certifications

. The prompt displays the custom list items.

You can use custom fields in calculated fields and condition rules. Condition rules that can use calculated fields can also use custom field data in their rule definitions. The rules include business process condition rules.

Calculated fields can reference custom fields, just like other fields from the owning business object.

Fields in a multi-instance custom object or a custom object that extends an effective-dated business object aren't in the primary business object for the report:

To report on fields in a...	Then...
Multi-instance custom object.	Select the custom object in the Business Object column of the report definition.
Single-instance custom object that extends an effective-dated business object.	Select Additional Data in the Business Object column of the report definition. You select custom fields in single-instance custom objects that extend an effective-dated business object from the Field Name column.
Multi-instance custom object that extends an effective-dated business object.	Create a Lookup Related Value calculated field related to the Business Object that obtains the Additional Data. The Return Value in the calculated field is the name of the effective-dated custom object. Select this calculated field in the Business Object column of the report definition. Select the custom fields in the Field Name column.

When you create a Lookup Related Value calculated field for multi-instance custom objects that extend an effective-dated business object, use these effective-dated business objects and their related Lookup Fields and business objects:

Effective-Dated Business Object	Lookup Field	Related Business Object
Worker	Worker Additional Data	Worker Custom Data Snapshot
Job Requisition	Job Requisition Additional Data	Job Requisition Custom Data Snapshot
Position Restriction	Position Restriction Additional Data	Position Restriction Custom Data Snapshot
Academic Appointment Track	Academic Appointment Track Additional Data	Academic Appointment Track Custom Data Snapshot

When the primary business object of your data source is Organization, create calculated fields on the Organization business object to access custom fields on specific organization types in custom reports. This includes custom fields for an organization returned by Lookup Organization. Using the

Look Up Related Value

function, select the organization type that the custom object is on as the

Lookup Field

. Select the custom field in the

Return Value

field. When using a multi-instance custom object, select the custom object in the

Return Value

field.

Security for custom fields in reports is the same as the security for other Workday report fields. A report creator can access a report definition custom field, even if they don't have View permissions for the custom object and field. However, the report creator can't see any data when they run the report.

Custom objects are secured to domains. When you create a calculated field that references a custom field, the calculated field security considers the custom field security. The calculated field also considers the security of delivered Workday fields that it references.

When a worker runs the report, they can see only the fields in domains to which they have View access. If the report contains a calculated field based on a custom field, the worker can only see the calculated field and values if they have View access to the domain that the custom object is secured to.