Liquid tag iteration through all the fields in a form

[kaido20]

I have a web form with multiple questions with the same options (Yes, Maybe No)

I am trying to use liquid tag to count the number of Yes, Maybe, and No in form responses.

I know that I can use a conditional statement for each entity, something like:

{% if form.field == 'Yes' %}

{% elsif form.field == 'Maybe' %}

{% else %}

{% endif %}

But then I would be repeating the same 6-7 lines of code for each form field.

Is there a way to use the iteration tag to loop through all the fields in the form? Something like

{% for fields in form %}

{% if form.field == 'Yes' %}

{% elsif form.field == 'Maybe' %}

{% else %}

{% endif %}

{% endfor %}

[OliverRodrigues]

Hi

Can you expand a bit more on your requirement?

I think you actually should be looking at JS/jQuery options here. Liquid is a server-side template language, what you need is to interact with controls on your page. Client-side scripting might be what you are looking for.

------------

If you like this post, give a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users find it.

[kaido20]

I have a webform, upon submission, users are redirected to another page that shows them a result based on their entry, so as far as I know, there are no JS/JQuery script that would work because I would run into the same issue that I need to be able to target all the fields in a CDS entity without explicitly naming the attributes. 

If there is another way to extract the answers from users' submissions, though, please do let me know. 

[Fubar]

On the page after the submit, use FetchXML (there's a liquid tag for it) to do the counting (the submit on the previus page saves the data to CRM so you can Fetch it on subsequent pages).  If prior to the pressing the submit then use JavaScript/JQuery.

[OliverRodrigues]

Hi

how do you need this "results" stored in CDS? do you need to have a summary/count of answers or simply having the answers itself?

if the former, I would consider adding additional fields in the CDS:

• Count of yes answers
• Count of maybe answers
• Count of no answers

finally adding a Plug-in and manipulating those.. in your summary page all you need is to display those count fields

in your plug-in this would still be hard-coded the attributes you are doing the calculations (unless you want to go via Entity Attribute Metadata and get the attribute types)

If you just need to display this in the results page, but not storing in the CDS, I see only the below options:

• via Liquid - you will have to hardcode the attributes to read the values
• via Liquid or Entity Form + jQuery/JS - you can render the attributes as they are, but keep them hidden in the form (if rendering via Liquid, you can add the display:none while rendering, if having an Entity Form, you can add JS to hide the section/attributes).. then you can add jQuery/JS looping through the boolean controls and performing your calculation.. finally adding a new element with the results

[justinburch]

I agree with @OliverRodrigues's approach here - use JS and an Entity Form, so that you reduce your technical debt. Even though @Fubar's suggested Liquid tag works, your FetchXML and Liquid objects will all be static definitions. As Oliver suggested, put all of the fields in a hidden section - the easiest way is to add them to a Section, set the "Name" to something such as "hiddenAnswerSection", and then add CSS to your files or Web Page like:

[data-name="hiddenAnswerSection"] {
  display: none; !important
}

But does it need to be hidden? You should be making the fields read-only, or the Step read-only, so the fields could act as a receipt.

Regardless, then you just iterate through each of the fields or the specific type. Code below assumes read-only fields of Option Set type:

$(document).ready(function () {
  // Replace 111 with Yes value, 222 with No value, 333 with Maybe value..
  window.AnswerCounts = window.AnswerCounts || {};
  window.AnswerCounts.Yes = $("[data-name='hiddenAnswerSection'] .picklist-cell input[value='111'").length;
  window.AnswerCounts.No = $("[data-name='hiddenAnswerSection'] .picklist-cell input[value='222'").length;
  window.AnswerCounts.Maybe = $("[data-name='hiddenAnswerSection'] .picklist-cell input[value='333'").length;
});

You could also make the variables as arrays, store the IDs of the selects, and use the length of the arrays as the counts - the options are many. 🙂

$(document).ready(function () {
  window.Answers = window.Answers || {
    Yes = [];
    No = [];
    Maybe = [];
  };
  // Not using the name of the section as a second option..
  $(".readonly.form-control.picklist").each(function (index) {
    if (this.value == '111') { .... }
    ...
  });
});

[kaido20]

I have been trying the solutions offered so far, though I have to admit I am quite new to portals and am maybe doing something wrong. 

1. I can't seem to create a separate section with all the answers. The fields I added can't be inserted twice, and when I create a separate form with the same fields, it just creates the same survey in the results page. 

2. I thought of using liquid tag to get the results in a div, and then use JS to count the number of yes, maybe, and no. But the liquid tag is getting a blank result. This is my code:

{% assign quickcheck = entities.crf67_quickcheckmitarbeiter['4eb19395-26d7-46cc-8db1-04b97c53af68'] %}
{{ quickcheck.crf67_structuredteammeeting }}

What am I doing wrong? 

[justinburch]

Hi @kaido20,

For 1:

To add the fields more than once, you need to uncheck the option "Show only unused fields":

Either create a new form or a new tab on the same form, and reference them in the steps. If you are using two Forms, then each Step should point to a different form. If the same form, after unselecting the option indicated above, create like so:

For 2:

Your Liquid is pulling in an Option Set object, which doesn't have a string equivalent. Try {{ quickcheck.crf67_structuredteammeeting.label }} (for the Yes/No/Maybe) or {{ quickcheck.crf67_structuredteammeeting.value }} (for the numeric Option Set Value).