InfoPath Dev

So - it is library 1a where the fields don't get populated? in library 1 they do? Are the XML in library 1a linked to the template in 1a? They aren't, right? They are just submitted to 1a. What happens if you relink one of the forms in 1a (under the Relink view in the library)?

If you look at your library columns under settings, are there duplicated promoted properties? I've seen that happen too. In the manifest, the promoted fields are found here: /xsf:xDocumentClass/xsf:listProperties/xsf:fields and the actual columns are here: ...

Internally in the manifest, there is a GUID for the promoted column - if they don't match, they get blanked out when you republish. Publishing from library to another may be causing the issue. One way to check is to open (you don't have to save / submit) one of the forms where data isn't showing. After opening the form, is the data now ...

Right, no IF rules in InfoPath. In the form designer, add a rule on the percentage complete field. Set the target field to In Progress. Then add two more rules - one with the condition that percentage complete = 0, that sets the target field to Not Started, and a final rule, with the condition that percentage complete = 1, to set the target field ...

Yes, set submit to overwrite and make sure whatever you are using for your form name is going to stay stable (i.e. don't use a function with now in it or something). If you want the datetime in the form name, have a field in your form for that and a rule that sets it only when blank, so it only gets set the first submit.

Do your users use the ribbon to save the edited form? We usually hide the ribbon or disable save / save as and don't show the submit button, then just put buttons on the form to submit so that we can have a close rule.

I'm so sorry, I had this thread confused with another - no wonder my last reply made no sense! Here's a blog post on using input parameters: https://blogs.msdn.microsoft.com/infopath/2007/02/26/passing-data-into-a-form-input-parameters/ - if code isn't an option (like if this is Office 365, or your SharePoint admins don't allow ...

If you mean setting a default instead of using a rule, you could start w/ what you are already using - just in the field's properties, set a default value. https://support.office.com/en-us/article/set-the-default-values-for-a-form-d1ffca72-fd68-4775-af6d-7d998df536b2 has more on that.

Again, I simply don't believe there is a good approach using the structure you currently have in place, with each field inside its own repeating section. That said, part of your issue may be that you are setting the field on it's own change - which is rarely a good approach. You should probably put your rule somewhere other than on the ...

Is this a Nintex feature, opening a specific view via URL? In InfoPath forms (not list forms, just regular library forms) the only ways to do this involve code (or qRules) to get an input parameter and switch the view.