The below is kind of like an issue queue of sorts.

  • I have a content type called 'requests'.
  • One node is created for each application.
  • Each node has many requests, the details of which are in a field collection shown as a table.
  • Each request can be 'completed' or not.
  • Given a view of all request nodes, I'd like to show all nodes, but inside each node, hide the field collection 'rows' which are (not) completed.

This would allow me to have two Views, one showing outstanding requests and another showing completed requests. Both would show some data from potentially all nodes.

Is this presently possible? If not, can you change this into a feature request?

Comments

rootical’s picture

rootical commented

subscribe

rconstantine’s picture

rconstantine commented
Category: support » feature

I've poked around and it isn't presently possible.

jason.fisher’s picture

jason.fisher commented

Maybe by embedding a view into a field of another view, using an additional hidden field from the parent to feed the child view argument.

rconstantine’s picture

rconstantine commented
Status: Active » Fixed

Well Jason's suggestion didn't work, but it did get me thinking, which did lead to a solution. I'll share it here for anyone else who'd like to do something similar.

I stated my use case above. The fields in my collection are simple -

  • Task Summary
  • Task Description
  • Requested By
  • Completed

For my purposes, I don't need to track details of the solution, any dates, etc. which a more robust issue tracker would include.

Previously, I was trying to use the Unformatted list type of node view since that would automatically group sets of tasks by node.

Instead, I'm now using the Table format and then hiding the Title and grouping by Title. This gives me multiple tables, just as before, each with my selected fields.

I only selected the following fields:

  • Task Summary
  • Task Description
  • Requested By

I then filtered on the usual - node is published and of the type I want - and then also added a filter on the 'Completed' field, which I had before when using the Unformatted format type, but which apparently operates differently for tables.

Boom! The results are now filtered. I have two tabs. One for completed = 0 and one for completed = 1.

The remaining question I have is this:
Why does the filter on 'completed' work when I use a table of fields, but not when I display unformatted nodes? The unformatted node scenario was clearly grabbing nodes and ALL rows of the field collection if ANY row in the field collection met the criteria, whereas this new method treats each row individually. This behavior, while acceptable since I was able to achieve my aim, is not obvious. Perhaps some further documentation is in order?

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.