What I'm trying to do is create a repeatable control with a textbox field for "Email", and drop-down list box for "Email Type". So if I add someone who has more than one email i can just add a new section for the email and email type otherwise if they only have one email I don't have to change anything.
Is there any way to create a repeatable control with multiple fields in infopath designer 2013?
I'm on an earlier version of InfoPath but I would guess that you should be able to:
Add a repeating section
Add a text box inside the section
Add a drop-down inside the section
Is this not sufficient?
Related
I would like to add a text field to all my forms programatically. There is a hook for adding hidden fields (wpcf7_form_hidden_fields) but I can not find one for regular fields. I tried modifying the form via wpcf7_form_elements which works, I get my new field. However it is not really part of the Contact Form 7 cosmos, I can not use wpcf7 validation on it.
Is there another way?
Thanks
In InfoPath 2010 there was a trivial manner to set the view called for an item based on the function desired, e.g. a separate view could be made for create, edit, and display and set as the default.
See here:
http://chanakyajayabalan.wordpress.com/2013/06/20/individual-newedit-and-display-forms-for-sharepoint-using-infopath-forms/
I cannot however find the equivalent for InfoPath 2013, nor am I able to locate the corresponding element via SharePoint Designer.
It also would appear that you cannot append the view to the URL in order to directly call a view.
Creating a rule for Form Load that detects some attribute of the call, and sets the view accordingly seems like another option, but I'm just not certain how to access the appropriate identifier.
Final resort would be to do away with the InfoPath form, and create/modify pages via Designer, but would rather avoid this if possible.
Found the way around this is edit the page in SharePoint. You can't do it in SharePoint designer anymore.
Create your views in Infopath then publish. After for the form you want to change the view on, IE create new item or edit item. Once there choose edit page from the settings menu, then modify the Infopath web part to use the the view you want.
This will work for additional forms as well if you want to add custom actions to the list.
I'm following collective.examples.userdata to add some custom fields on the register form.
I want to add two fields, one for state and another for city, where the second load content based on the previously selected state.
My question is how it is possible, can do this only with the schema, using dynamic vocabularies or is need to edit registration form? How can I do it?
Another issue is how to load the registration form in a portlet. Is Possible fill the ##register viewlet?
Thanks!
Use javascript to do the dynamic part of the secondary field. To render the form inside a portlet, there are a couple of ways to do it but again, using javascript might be the easiest. You have place a register button that opens a registration overlay.
Take a look at http://plone.org/products/plone.app.jquerytools for how to wire it up.
The Defalult fields are #,SUBMITTED,USER,IP ADDRESS...
I need to add an extra field as Deal Title & Expiry which are the fields I have added for my webform, can anyone suggest a way to do it?
There is a module named - Webform MySQL View
Steps:-
Enable the module
URL: Base_URL/admin/content/webform/mysql
Click the MySQL Views tab
Check the boxes next to the names of the Webforms for which you want to create MySQL views
Submit the form.
Once you have created a MySQL view for a given Webform, the view will be automatically updated whenever you add, remove, or reorder the components for that Webform.
Try this, it's easy.
I have an infopath form, is there anyway to get this current infopath form and once submit is clicked, have it go to another form or show a different set of fields upon press [submit] ?
Thanks
If what you want to achieve is some kind of multi-step form, you could use views. InfoPath Views allow to display different fields depending on the view, and you can add buttons to navigate from one view to an other. You may also evaluate some rules before switching to an other view (for example to check for mandatory fields).