InfoPath Dev

 I've started playing with the "manage multiple items" form option...but having trouble wrapping my brain around how to make it do what I need it to do. In simple terms, the repeating sections let you set up some fields like so: HEADING 1 Record ID 01 - not displayedSet Field 1 Value 1 (chosen from dropdown with filter ...

 Thanks!!!! It solved the problem

Under the File menu in InfoPath Designer, look for Advanced Options. Under Versioning, you can check to see if Update Existing Forms is set to automatically update.

Hi, I'm new here. I'm having a problem when adding any fields to a form.   First: I created a document library...Created the form in InfoPath 2010... added some records... Now I want to add more fields to the form..   The problem i'm having is that the added fields is enabled when create a new record... but in the old ...

 I have a form with buttons in a table.  These buttons change values of options and hide/show sections in the table.  For one user, the buttons are truncated, so they can't see the full label of the button; I can't figure out why.  I tried rebuilding the table, same end result; the buttons are truncated for the ...

It seems odd to me too - I know when we query a secondary data source, rules on fields don't fire after the query. It isn't considered a change. So yah, I'm surprised to hear the New Record does act as if fields have changed. That said, at least you know what's going on and can work around it. Oh - I agree about the value of being ...

All my rules were set to when field changes.  I have now set them to when field is not blank and that seems to have solved it, I will continue to play to make sure.  Seems strange to me that the new record button counts as a change, I thought it was effectively reloading the form as new. Thank you so much for your help!  ...

Yah, I'm not sure - the only time I get that error on a form with code from DAT is when the instance of DBXL is not in my local intranet or trusted sites in my IE settings.

Good detective work. So, one thing about rules that people don't always realize (forgive me if I am telling you something you already know) - rules fire when the field they are on changes. So if field1 is equal to B and you have a rule that fires on field1 with no conditions, it will fire every time field1 changes.... but, if you set field1 to ...