Relationship using term reference

Hello!

To me it sounds like you need an exposed filter or argument on the webform submission. Argument is not available yet. Filter - seems like yes according to my quick test.

Nonetheless I will take this opportunity to write a relationship from a referenced entity in a webform submission to its base table. So you could do to the term reference (in your example) and then place some field from the term into the view result.

hello! :)

Your patch 0001-Correct-incorrect-grammar-in-help-messages.patch definitely goes in :)

As for 02 and 03 patches of yours, I would prefer to use my patch from #2 because it solves the problem on a more generic level - for any webform element that implements entity reference interface. With such approach with a single views data class I have covered term select, entity select, entity autocomplete (and possibly even more element types). Does it make sense to you?

Hi.

First, thanks for the module.

I take this issue to ask for help on a view with which I'm having problems adding a contextual filter that filters the webform submissions by the node's author from which any user can send the webform.

The webform collects all the necessary values of the node (author ID, node ID, author name, ...) and the view shows them perfectly.

Problem: the author of a node can see all webform submissions sent from any node (even if he isn't the author).

Therefore, it would be necessary to add the contextual filter that filters by ID of the identified user. That way, each author could see only the webform submissions made from their own nodes.

I hope you can help me, because I have tried "a thousand" options and I can not find a way to solve it.

I have applied the patch in #2 and the first of #3.

Thanks.

hello, geYdes!

Your problem hardly fits into this ticket. You do need a contextual filter on author of the webform submission if the "user" is part of the URL. But if you just wanna limit to the currently logged in user, then you should add a relationship to the user and then use a filter "current user" or something like that (I do not recall how exactly it's called).

As far as the main topic of this ticket, I've just committed my #2 + 0001-* patch from #3. As I haven't got feedback from NigelCunningham and there was some time I decided to move forward with the commit.

Thank you for patches, NigelCunningham!

Hi, @bucefal91.

That's the question, find a way to establish the relationship that allows me to apply the contextual filter to the current user.

But the relationship is not possible to establish.

Thanks!

NigelCunningham, no problem at all :) I also lose emails now and then

geYdes, I just had a random view of webform submissions - there is an option to add a user relationship. I believe you do not even need this module (bare bone webform.module will do it). See printscreen enclosed.

Yes, bucefal91, this module is very necessary in this case, and others, because it allows managing the display of results with a wide range of possibilities. With Webform only is not possible.

And yes, the "User" relationship already exists, but it only allows associating it correctly with the user that sent the webform.

In the case of needing to establish the relationship with the node's author from which the webform is sent, the established contextual filter breaks the view, showing no results.

This is the problem that happens and why I raise the issue.

In any case, thanks for the module!!

oh now I see. Your "user" is not the author of the webform submission but author of the node where it was submitted. In that case you have to build your view off the "node" table. Right now it is impossible to build a relationship from webform submission to the source entity. Do the following:

1. Create a view on "content" (aka "node) table;
2. Add relationship to the "webform submission" (see the screenshot where I highlight the correct relationship);
3. Add relationship to the "user" from the node author;
4. At this point you should be set as far as the problem you're speaking of. You can "cook" the rest of the view per your specific case. And yes, in this set up you will need Webform Views. I just didn't understand your problem in full at the 1st glance.

As far as I understand your question, the above is the answer you need :) well, there's still some chance I misunderstood it again :)

I've just filed a ticket to introduce the relationship from "webform submission" to "webform node". It is #2950742: Relationship from submission to webform node.

But as I said, geYdes, my steps from previous comment should already get you running (as long as you can afford to build the view off the node and not off the webform submission).

Perfect!!

I'm going to do it that way and I'll comment on the result.

Thanks!!

Hi, bucefal91.

I confirm that following the instructions in #12 the issue is fixed.

Thanks!

geYdes, 8) next time you come across a developer on the street, buy him a beer.

Better to two... ;)