How Custom Fields Work in Wrike Analyze

TL;DR

Natively, Wrike Analyze stores task and project/folder custom fields in separate linked tables,with all fields at each level sharing one value column. Filtering by a custom field limits the entire table to that field, so standard widgets support only one custom field name filter and can’t show multiple fields as separate columns. Ensure fields are shared with everyone, use the correct item-level dimensions, and include only existing values. Use columnar custom fields to work around multi-field and blank-value limitations.

• Overview
• Custom Field Data Tables
• Custom Field Filters
• Multiple Fields in Pivot Tables
• Custom Field Checklist
• What’s Next?

Overview

Wrike Analyze stores custom field data in linked data tables. Understanding this structure can help you choose the correct dimensions and identify why some widgets can’t display multiple custom fields.

Custom Field Data Tables

Wrike Analyze uses separate custom field tables for:

• Tasks
• Folders and projects

For example, Task Custom Field is the table for task-level custom fields.

The dimensions listed under it represent the table’s columns, such as:

• Custom Field Name
• Custom Field Type
• Custom Field Value
• Custom Field Date value

The data in each row depends on your account, but the table structure remains the same.

Custom Field Filters

When you filter a widget by a custom field name, Wrike Analyze filters the entire custom field table to rows associated with that field.

For example, if you filter a widget by a multiselect field, the widget can only use values from the selected rows. Adding a date value dimension won’t return results if the relevant date fields exist in other rows.

Multiple Fields in Pivot Tables

You can add several field names to one filter. However, Wrike Analyze displays their values as additional rows in the same custom field column, and it doesn’t create a separate column for each field.

Because all standard custom fields at the same item level share one table, a widget can use only one custom field name filter.

To display custom fields in separate columns or use several custom field filters, consider columnar custom fields.

Custom Field Checklist

Before you build a widget:

• Share each custom field with everyone. Wrike Analyze doesn’t export fields shared only with specific users.
• Use dimensions from the correct item level. Task fields and folder or project fields use separate tables.
• Use only one custom field name filter in a standard widget.
• Add only existing custom field values. Standard custom field tables don’t store blank values.

What’s Next?

• Add columnar custom fields to Wrike Analyze
• Build formulas in Wrike Analyze
• Advanced Reporting: Available Data – Wrike Help Center