-
So - in your code, you create a new row in your repeating table? With all the fields? What's your code look like?
-
Great news! Glad that fixed it!
-
How is your code creating the rows? Is the new field included in that code? Or do you have default rows added that you are populating, in which case under Default Data, the new field may not be selected to be included by default.
-
Yeah, this is one of those things that you end up having to manually create. I use the formula editor to see if I have my syntax right. But there isn't an option in the first dropdown to add a filter via the UI.
-
In your InfoPath form, right click on the Class dropdown and select the dropdown properties. On the first tab, you'll see the data source is your class list, the value is the ID, and the display is the Class. So, in the list that your form is bound to - Class is a lookup. SharePoint is going to store IDs in the lookup column - this is because ...
-
Just updating this thread with what we learned via email. In your case, the duplicated columns were NOT associated with the content type for the library. You went to /_layouts/mngfield.aspx (to see the site content type columns) and deleted the ones that were not associated with the content type. SharePoint didn't let you delete any columns ...
-
OK! So, here's what I think your issue is. The Class dropdown displays the text in the title of the list it uses for the lookup - but the actual value is the ID. I don't understand how your attempt with the full text was working in this scenario, but I'm attaching a copy of your form that I *think* will work correctly. If it ...
-
With option 1, just add a button (or buttons, you can get fancy & make them arrows or something for show hide) that sets a query field in the secondary data source with the "child" data and runs the query. Usually, I'd drag the data fields section from the secondary data source onto the form, with a section around the repeating ...
-
You are creating a SOAP connection, right? Not accidentally selecting REST? EDITED TO ADD: I missed your additional response! Glad you have it sorted out.
-
My setup has changed since I last posted versions - when I set up my new machine, I went w/ 32 bit Office for both InfoPath 2013 and Office 2016. I can't reproduce any of this, I'm afraid. My email submit pops up an un-editable email window. If I save a form as 2007 compatible, it works as expected as well.... any of your forms using code? ...