InfoPath Dev

That is correct - this is because that approach uses a script web part, which is added to a web part page. Each view has its own page, thus the script web part has to be added to each view.

Yes, it is a list form, so I was assuming that. I can see it has a view for new and one for edit. If it isn't used in a web part, I'm not sure how it is getting switched. There's an option in the Form Options for setting the Display View, but that won't alter the New Item / Edit Item scenario. You may want to check the list in ...

Is this form used in a web part, by any chance? I don't see any logic to change the views in the Form Load, which is where I was thinking they might be.

I'd need to see the form. You can attach it under the Options tab in a reply.

Put the fields in the section, and hide it unless the Add More Parts field is equal to true?

Wonderful, so glad that did the trick. Can't tell you how many times I've gotten stumped on that kind of filter, I'm glad I was able to help you. :)

Hi, welcome. I always struggle with this type of filter too. I think that what you need to do is use the "equal to" filter and then change the first dropdown where you build the condition to "the expression". Then, put parenthesis around the text in the expression builder and the word "not" before it, like: not(field1 ...

I'm sorry, I'm having a little trouble understanding this question. If you have a document library, and need to make some fields required, you can do that in the library settings.

If these are in a layout table, you may need to set the table row height to "auto"

Use sections - they can be bound to any field, including the root, so no need to add a bunch of fields for your sections (not sure if this is a list or regular form). Then use conditional formatting on the section. I'd probably add a field for tracking status, no need to put it on the form. When the form is new, Status will be blank. Parts two ...