When you link two lists together using Infowise Associated Items it's useful to pass data from the Parent list to the Child list. In this example I have two lists tracking parents and their children and I setup a Default Values and Dynamic Rules to copy data instantly from the parent item to all child items.
The Parent and Child lists have these matching fields:
- Parent Name
- Parent Age
- Parent Phone Number
Duplicating these fields in the child list gives the Default Values and Dynamic Rules a location to copy the data too.
Infowise Field Name
The Default Values and Dynamic Rules need the Infowise field name for each field it being passed from parent to child. This field name is a combination of the prefix iwfv_ and the SharePoint field name.
You can find the SharePoint field name by going to the parent list settings and clicking on the field to get to the edit screen. The name of the field will be in the URL on the edit screen. In this image you can see I find the SharePoint field name for Parent Age:
Now I add the prefix iwfv and which gives iwfv_Parent_x0020_Age. This is the text that to use in the Default Values and Dynamic Rules settings.
Default Values and Dynamic Rules
Configure the default value inside the child list by clicking on the Design button and going to Infowise Ultimate Forms.
Click on Default values and dynamic rules
For the Column configuration choose the corresponding child field Parent Age. Check the Parameter checkbox and enter the Infowise field name iwfv_Parent_x0020_Age.
Click the Add button and you have the default set and the data will be passed from Parent to Child by default.
Using Infowise Associated Items and Default values and dynamic rules we can pass data from the parent to the child. This advanced technique is useful if you want to build reports in child lists that contain parent data or execute Infowise Smart Actions from child lists based on parent data.
5/22/2017 6:01 PM
12 comments [latest: 6/22/2017 5:47 PM]
[4/26/2017 5:06 PM]
I'm having trouble getting this to work on-prem and I the video and screen shots appear to be using the O365 version of InfoWise. Does this work on-prem and are there any differences? I set up this exact example and the default is not being applied when I create a new child item from the parent list.
[4/26/2017 7:38 PM]
Matt: it works almost identical, on premises we use iwfv instead of iwfv_, but that's all.
[5/9/2017 12:33 PM]
I tried this out, but it doesn`t work at all. I put it together like shown in the vid. But the data weren' t passed to the child list. We are using a SP Foundation 2013 on premise with IW Ultimate Forms Suite. I am the owner of the site without any restriction rules. The item in the child list is added by using 'New entry' in the parent list column, while the parent list is in 'View' mode
(btw. same result on 'Edit' mode).
The complete SP-URL of the Parent field looks like this:
The Default Value in the child list was set to "iwfvvollst%5Fx00e4%5Fndiger%5Fx0020%5FName" as shown in the Video and according to the recent post concerning difference between Office 365 and on premise.
I think that' s right, but it doesn't work. The shown parent field is a calculated column and concats two other parentlist-Fields (result Format: single line of text).But it doesn't work either with a single line of text field where the value results from user input
What is wrong? Do you have a hint for me to make this work?
[5/11/2017 8:36 AM]
Peter, this functionality will work only in new or edit form.
the logic that is collecting parent field values is working from the client side and taking the values from field controls, so if your parent field is a calculated column it will not appear in these forms and its value will not be passed to the child.
for more information, please contact our email@example.com
[5/11/2017 1:54 PM]
Genady,thanks for your advice. But as mentioned also a user Input field doesn`t work . Which list / item has to be in 'edit'-mode(Parent and/or child or both)?
[5/11/2017 7:51 PM]
Peter: the parent needs to be in edit mode (or new). Not all field types are supported in all versions.
[5/12/2017 6:34 PM]
Can you please tell us what field types ARE supported? I have attempted to implement this as well on ALL field types and it does not work - no errors, just does nothing. Please provide additional explanation and/or training.
[5/12/2017 7:28 PM]
Toni: generally, editable fields, such as text, number, date, etc. should work fine. Note that when there are a lot of fields in the list, not all of them can be passed due to URL length limitation, so use field ordering of the list to put the fields you want to pass first.
[6/21/2017 11:03 PM]
I too have on-prem 2013 Foundation and Ultimate Forms. This doesn't work. I have used all the comments above to no avail. No matter what type of field, regardless of new or edit form, this isn't working. I have ordered the parent and child fields to the top of the list...nothing. I would love to make this work, but On Prem users need different instructions.
[6/22/2017 2:03 PM]
Jon: the only difference between O365 and on-prem, that on-prem the prefix is iwfv (without the following underscore), e.g. iwfvTitle, not iwfv_Title. You can examine the URL with which the child form opens, the values will be in the URL.
[6/22/2017 5:42 PM]
I think the issue has something to do with spaces in names. I finally made this work when the parent field name was only a single word (or if I put an underscore in place of a space). For example I can pass through a field called test_text, but test text doesn't work. I have tried iwfvtest%5Fx0020%5Ftext, iwfvtest text and other variations. Any thoughts?
[6/22/2017 5:47 PM]
Disregard my prior submission, I replaced the space with _x0020_ and got it working. Thank you.
Comments are not designed to replace support calls. If you have a specific issue with one of our products, please send an email to firstname.lastname@example.org
to open a support ticket.