Report on Custom Fields in Wrike Analyze Without Columnar Fields
TL;DR
Report on multiple custom fields by using field names as pivot rows or field types as separate columns. Numeric fields can be charted and compared. Limitations include one custom field filter per widget and missing null/untouched values; new storage columnar fields can help.
Table 34. Availability - Legacy plans
| Availability: Pinnacle, Apex. ; Unavailability: Free, Team, Business; |
- Overview
- Check Your Storage Type
- Use Field Names as Rows
- Separate Fields by Custom Field Type
- Report on Numeric Custom Fields
- Limitations
- What’s Next?
Overview
You can report on multiple custom fields without using columnar fields. These methods work with both standard storage and new storage and can help when you have many custom fields or need to report on multiselect fields.
Check Your Storage Type
Open any analytics board and check the upper-right corner:
- If you can refresh the board or create a public link, your account uses new storage.
- If you don’t see these options, contact Wrike Support to ask about new storage.
Use Field Names as Rows
This is the simplest way to show several custom fields in a pivot table:
- Create or edit a pivot table widget.
- Add the Task Custom Field Name (or Folder/Project Custom Field Name) dimension to Rows.
- Add a widget filter.
- Select the custom field names you want to include.
Separate Fields by Custom Field Type
Use this method when your custom fields have different types and the total number of field options is manageable.
- Filter the widget by the custom field names you need.
- Add the corresponding field-type dimensions to Rows.
- Rename each dimension to match the custom field it represents.
For example:
- Rename Task Custom Field Text Value to “Impact”
- Rename Task Custom Field Numeric Value to “Budget”
Each custom field appears in a separate column.
Report on Numeric Custom Fields
If all the custom fields in your widget are numeric, you can add them to Columns. For charts, use Break by.
For more control and to exclude blank cells:
- Add a separate value for each numeric custom field.
- Filter each value by its custom field name.
- Add formula-value filters to exclude blank values.
This method lets you use a separate formula and filter for each custom field.
Limitations
Dashboard filters
A widget can’t use more than one custom field filter. This can cause conflicts when a board contains several pie charts filtered by different custom fields.
For example, selecting a slice adds a board-level filter. Other widgets may already use their own custom field filter, so Wrike Analyze can’t apply both filters.
Null values
Standard data tables store only existing values. When you filter by a custom field name, Wrike Analyze excludes tasks, folders, and projects where that field has no value.
This also affects checkbox fields. An unchecked box appears as false only after someone interacts with the field and sets its value to false. If no one has interacted with it, no value exists.
Tip
Columnar fields in new storage can help address these limitations.
What’s Next?
Was this article helpful?
Thank you for your feedback.
Thank you for your feedback.
Please sign in to leave a comment.