[From Wrike] Behind The Scenes of Custom Fields in Wrike Analyze

Hi Community,

Iโ€™m Herine, Wrike Analyze Subject Matter Expert from Support ๐Ÿ‘‹ย  I hope my previous post on calculated custom fields came in handy!

Now Iโ€™ll show some of the backstage magic and shed a bit of light on the skeleton of Wrike Analyze ๐Ÿ™‚ I believe you will benefit from reading this piece if:

  • You want to report on multiple custom fields or show how they are correlated.
  • Youโ€™re looking for some technical background in custom fields analytics.

How custom fields are structured in a data model

Data displayed in Wrike Analyze is stored in analytics databases. Theyโ€™re grouped in data tables that are linked with each other forming quite a complex data model. This is what a data table looks like in the Wrike interface:

โ€œTask Custom Fieldโ€ is the name of the table, and the dimensions below are its columns. Hereโ€™s what the table looks like in the data model (this view is not available in the Wrike interface):

Data in the rows are unique to each account, but the structure of the table is the same.

Why is the structure important? It explains why itโ€™s not possible to filter a widget by more than one custom field.

For example, letโ€™s say a widget is filtered by a multiselect custom field type. The whole Task Custom Field data table will be filtered to it:


Now itโ€™s not possible to display anything that falls outside of that green selection. Once the widget is filtered to multiselect custom fields, it will display only them. If, letโ€™s say, โ€œTask Custom Field Date Valueโ€ is added to the same widget, the widget will show no results since the relevant date fields live in other rows.

Limitations: only one filter per widget

Therefore, itโ€™s not possible to add custom fields as separate columns to a pivot table: the widget needs to be filtered by a field name, and since thereโ€™s just one custom field data table, there can be only one custom field name filter:

Of course, several names can be added to the same filter, but that will just add more rows to the same custom field column and will not break it into two:

What can be done to put custom fields in different columns? In my future posts, Iโ€™ll share two types of workarounds, depending on the analytics database type of your account.

And as a bonus, hereโ€™s a checklist of a few important things that should be kept in mind when working with custom fields in Wrike Analyze:

  • Custom fields should be shared with everyone (fields shared with specific users are not exported to Wrike Analyze).
  • There is a separate custom field data table for each level: one for tasks, and one for folders/projects. Itโ€™s important to use dimensions from the correct level.
  • *There can be just one custom field filter in a widget/board.
  • *Only existing values live in custom field tables: itโ€™s not possible to report on blank values.

*These limitations can be avoided, see how in the next posts.

I hope you enjoyed diving into some tech stuff with me!

Herine Community Team at Wrike Wrike Product Manager Infรณrmate sobre las funciones y prรกcticas recomendadas de Wrike

Herine Wrike Team member Infรณrmate sobre las funciones y prรกcticas recomendadas de Wrike

๐Ÿ‘ Spot On ๐Ÿ’ก Innovative Approach ๐Ÿ’ช Stellar Advice โœ… Solved ๐Ÿช„ Remove Kudos
0 comentarios

Can you help? Answer the question and work your way towards becoming a Wrike Ninja ๐Ÿฅ‹ Sign in and answer.

Iniciar sesiรณn para dejar un comentario.

Folllowing List for Post: [From Wrike] Behind The Scenes of Custom Fields in Wrike Analyze
[this list is visible for admins and agents only]

Didnโ€™t find what you were looking for? Write new post