- CharlieAnswered on December 30, 2016 at 05:06 AM
I am not quite sure if I understood your concern correctly here.
The "Postal Code Search" widget only has one output based on the current structure that it has. Could you please provide us more information on what you would like to accomplish? Do you wish to format each parts of the field using field IDs as a selector for CSS? If so that is possible. Below is a screenshot showing that the parts of the widget is broken down.
We'll wait for your response.
- VolleyballQLDAnswered on December 30, 2016 at 09:38 PM
While that is interesting and I may look at it later, I was not interested in formatting the separate parts via CSS.
When in form builder in the properties of a field with multiple parts you can find out the field ID for each part. So for example if using jotform's Full Name field you get two fields called first name and last name. In Properties - Advanced there is a button called Field Details and it shows the field IDs for the two fields - #first_1, #last_1. Similarly the Date of Birth field has three field IDs #month_4, #day_4, #year_4 and jotform's address field and so on.
So there are ways to use these separate fields in the forms (e.g. substring) and I was hoping to be able to do that with the postal code search input. However it just has one field ID - #input_63.
- BorisAnswered on December 31, 2016 at 07:28 AM
Thank you for the clarification on what you are trying to achieve. Unfortunately, it is not possible to get the value of any of the individual fields from within the Postal Code Search widget and use it in other widgets.
The reason for this is that each widget is loaded inside its own iFrame on your form - essentially, they are like small separate boxes or pages inside a form. The widget needs to be separated in such a way from the rest of the form due to all the custom scripts and functionality it has to provide, in order for its functionality not to create conflicts with the rest of the form, or with any of the other widgets that all provide a different set of functionalities.
So in order for all this to work smoothly and without conflicts, widgets with any type of "advanced" functionality have to be boxed inside their own iFrames. A widget performs its task inside its own iFrame, and only communicates the result of its work back to the form.
This is why many widgets do not work reliably with conditional logic, and why widgets cannot reliably use data from within other widgets. One widget does not have access to another widget directly, but it can only see the result that the other widget provided.
Substring widget cannot access individual fields from within the Postal Code Search widget. It can only see the result that this widget provides, which it can fetch from field with ID #input_63 on your specific form.
Please let us know should you need any further clarifications. Thank you.