-
Sounds like you have your setup basically correct - you should drag the secondary data source onto the form so you can see the data. Is ID number a number data type? It could be that added decimals are causing an issue.
-
This is hard for me to understand w/out seeing the form, but you may need to try using the checkbox on action rules to not run following rules if the condition is met. It could be the way you have them set up, all the rules are actually running and the status is being changed several times. But I'm just guessing.
-
What should happen if the user then chooses a different project for a row? Does this just happen when the first instance of project is changed? What if the user has selected a project for the first row, then edited the project in some of the rows, then changes the project in the first row?
-
So - I think you may have made an error and set the rules for item 5 on the extendedDate field? Rules run when a field changes, so you would want the rules set on managerExt and directorExt instead. :)
-
Yeah, that is an InfoPath browser form bug with calculated values. Will the form publish anyway? I think it won't block you from publishing. Edited to add: If the error bothers you, add a field w/ a default value instead of using a calculated value and display that instead.
-
Happily! I even have a forum set up for it here: https://www.infopathdev.com/forums/192.aspx
-
A promoted field is a field in the form that also shows in the library. Here is a blog post on these that may help you: https://support.formotus.com/hc/en-us/articles/201042367-How-to-promote-fields-in-InfoPath-2010-2013
-
I think you are fine here. I would only have worried about data loss taking the approach you did, but it sounds like you already knew which records needed to have the new option selected.
-
The only out of the box way to write data from a form to a SharePoint list is to use a list form. If you want to use a library form, you can use code or CAML (if you aren't using SharePoint Online) or third-party options like qRules or FormsViewer.
-
Since you are setting all instances of the "filter" field using your buttons to filter, perhaps current isn't needed. As to your question on the automatic IDs - it can be done. I don't recommend it, because without code or a method to "reserve" an id you can't guarantee uniqueness. In general, people add a query ...