If I add the primary field of an entity as column to the view (e.g. first column) this column is always handled as link.
As a result the user can open the appropriate document via a single click in the first column.
If I don't want to add the primary field to the view the user can't open the document as usual. He has to double click the record.
So, is it possible to add this "primary field column" behaviour to a normal field column?
Solved! Go to Solution.
No, unfortunately you can't do this; only the primary field column works this way. Is there a reason why you don't want to have the primary field column in the view ?
It is quite common to use a workflow to populate the primary field column based on others to give a useful name that can be used (you can't use a calculated field for this, as the primary field column cannot be a calculated field)
No, unfortunately you can't do this; only the primary field column works this way. Is there a reason why you don't want to have the primary field column in the view ?
It is quite common to use a workflow to populate the primary field column based on others to give a useful name that can be used (you can't use a calculated field for this, as the primary field column cannot be a calculated field)
Thanks @DavidJennaway for clarification.
In my case the primary field is made up of 3 different other field values (calculated using a plugin).
It seemed better to me to show these 3 fields individually in the view (e.g. sorting) and to do that without the primary field (redundancy)
User | Count |
---|---|
25 | |
4 | |
4 | |
3 | |
3 |
User | Count |
---|---|
26 | |
10 | |
9 | |
9 | |
7 |