Hi - this is a fascinating project - great work.
Am trying out in OA - have a GraphMind where nodes are Drupal User, and the next branch from each of users needs to be a display of Cases that have been Assigned To them.
I have a View constructed with 'Assigned To' as an Argument.
When I "Add Views List" to a User in GraphMind and select the Views and add the Argument for the User ID the nodes that get shown are the same for each User.
So obviously I don't have the Argument working correctly. (I have been following the youTube screencast http://www.youtube.com/watch?v=5_mVw_j1ukk
In Views, when I add in the User ID in the argument in preview the rows it returns the correct results (ie just shows the cases assigned to the user) so the Views bit is set up correctly for normal usage.
But to make this work in GraphMind
- do I need to have the Argument set up in Views (as I have done - i have tried removing it but no difference)
- am I right in assuming it pulls the info from the Default display (not that i can see how this would affect it)
- can you suggest what step i might have missed, or done wrongly, or have i hit a bug or non-existent feature?
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | Picture 121.png | 18.63 KB | petednz |
| #1 | Picture 119.png | 15.97 KB | petednz |
Comments
Comment #1
petednz commentedCouple of screengrabs in case it helps. Of course the thing I am needing is that it shold be applying the "casetracker_case_assign_to" rather than the User ID which it is pulling in if i "Add Drupal Item = User" - so i expect my logic is failing at several points.
I had already tried "Add Views List' to a non 'user' node - ie I had just created some nodes called 'pete' and 'chris' and had then added a branch with 'add views list' for the relevent Views with the Argument that correctly applies the 'assigned to' person when I am testing in Views Preview - but that also had returned the same results - ie the list of nodes that were exposed were the same regardless of the 'argument id' i put in.
Comment #2
petednz commentedOkay - so i tested with a different view outside of OA and arguments work as expected - used that same view in OA and it worked too. So will put it down to something in the other View running interference.
Comment #3
petednz commentedWOuld be keen to know if multiple arguments can be handled though, tried using same approach as in Views but no joy - is failure on this to be expected
Comment #4
itarato commentedHi,
I don't really understand, what you want. I tried multiple arguments in GraphMind: I made a views (simple node list) with argument (nid) and gave the concatenated node ids as argument (like: 34+35+123 or 34,35,123) and it worked. That's what you want?
Regards,
Peter
Comment #5
petednz commentedHi - I am trying to apply to one list a combination of Arguments that are defined in the View
- Argument = Assigned to
- Argument = Case Priority
so that the list in Graphmind would be able to show just the Priority A cases for Person B
I tried just using comma separted ie 1,2 so that it applies the first Argument then the second one but had no joy.
I think you are describing using the Argument to 'filter' within the list - after all it would be unlikely that any View you built would have 123 Arguments ;-)
Comment #6
itarato commentedHi,
Ok, now I get it. So you have more than one arguments in Views. In this case, unfortunately GraphMind can't handle more than one Views arguments. Yet. Currenly I'm not sure about if it's possible through Services, but I'll take a look at the specs. I will inform you about what I found.
Regards,
Peter
Comment #7
itarato commentedI don't have too much time to do this so any help would be welcomed.
Comment #8
itarato commented