By ojchris on
I want to embed a form into a content type where the field values in the form (attached to the respective nodes will be) will be:
1) compared to the values in the nodes of a separate content type.
2) used in Views to generate specific views pages.
Based on these two bulle points I am wary of using paragraph as my search indicates paragraph fields are either not accessible in Views or difficult to access. The other option I see is use Webforms but I'm how the data is stored and how accessible the webform fields values are to the Views module.
Any suggestion is appreciated.
Comments
You may look at these: https:
You may look at these:
https://www.drupal.org/project/entity_reference_revisions/issues/2799479
The 'Webform Views Integration' module.
Also, it's interesting to know the real use case.
The issue you shared is very
The issue you shared is very interesting as it confirms my hesitation to continue without asking for direction.
The use case:
Stage A
1) The content type has a conditional field where a boolean choice determines the next section displayed
2) The section presented in (1) will be a form (which holds standardized industry values expected from an investigation report)
3) The form, along with other existing fields of the content type is submitted to create a node.
Stage B
1) Another content type (thinking it could just be another webform) provides fields to enter actual result values from an investigation.
2) The result values from (1) is then printed on a report. A section of the report automatically provides a status highlight from comparing these values with that from with A(2) above. e.g. Red box indicates it's other of range, Green box it's within range.
Stage C
1) Pie/Bar charts related to the investigation per user is generation over time as required, which is also why we need to be able to access the values effortlessly.
I hope I made some sense.
Does a form should be
Does a form should be attached to a node view page?
If yes, could you explain how do you can use the Paragraphs for that?
Not sure I get your question
Not sure I get your question clearly. Can please clarify?
Let's say the is the node
Let's say the is the node with id=1.
You can open the node View page if you visit:
/node/1
Also, you can open the node Edit form if you visit:
/node/1/edit
On which one of these page do you need to add the form you talking about?
If this is '/node/1' page, then interesting to know how will you plan to use the Paragraphs.
If my research and the issue
If my research and the issue you shared, I will not be using paragraph. Webform seem a better approach. so long as I can access the webform field values in views using the Webform Views Integration module.
The form will be added to the edit page of the node using the entity_connect module but not to the node view page.
It seems the 'Entity connect'
It seems the 'Entity connect' module enable to create a new webform, but you need to render a form that is created. Or I don't understand something?
Why don't you want just add additional fields to a node?
The fields is already over 30
The fields is already over 30 fields long
If you don't want to use the
If you don't want to use the 'Paragraphs', then what about to refer to a node of special content type and using the widget provided by the 'Inline Entity Form' module?
I would really have preferred
I would really have preferred paragraph cause I can reuse the fields across different nodes but accessing the paragraph field values is not feasible.
Alternatively as you say, I could go with creating a reference content type and using the inline widget for display. My problem with this approach is the fact that the form content will be displayed in the content section (siteurl/admin/content) of the dashboard.
accessing the paragraph field
What steps must I do to reproduce this issue?
(the problem I met early was if I created a view that display paragraph that I can't display fields of a parent node. But, in that case, it was fixed with the patch form the #2799479 issue).
Oh I was seeing that the
Oh I was seeing that the patch broke some sites. I'll try the patch 8 and/or 108 and revert.
My problem with this approach
What about to use the 'ECK'?
Never used it, will check out
Never used it, will check out the video tut referenced. Thank you.