Hi all,

I have an upgraded form that I've tidied up massively, and removed all the things that would make it not compatable with web form services, but I still have two "Dialog box actions are not supported" in the design cheker (they are warnings) but they seem to be stopping the browser form displaying... any ideas on how or why this might be happening or how to find the mysterious things that its complaining about... its not a complex form so I'm a little stum

Hi noJedi- I assume you're talking about an InfoPath form from your description. Do you have rules set on the fields? If so, try removing those. If not, try removing the fields, save the form and see if it works. Then re-add the fields and re-save the form.

One more thing- is this a web browser form/did you change the type of form? Check out this link that shows dialog boxes aren't supported (almost to the bottom of the site):

https://support.office.com/en-gb/article/InfoPath-2010-features-unavailable-in-Web-browser-forms-f917032d-11cd-4b04-a9af-875165430985?ui=en-US&rs=en-GB&ad=

Hi,

Yes sorry InfoPath form indeed... InfoPath 2010 at this point.

there is one form and several rules on various things... its and upgraded form... it USED to be Filler only but its switched to web browser now...

I exported the file and took a look at the manifest.xsf file and searched for "Dialog" and there are a bunch of <dialogMessageAction> in a section "<xsf:ruleSet name="ruleSet_8">"

I also noticed a bunch of references to old fields in this set that are fields that have been deleted...

Have I done something wrong or am I missing a step?

I can't see these anywhere in the InfoPath UI... rule inspector has only a few (current) things listed...

I did delete a couple of views... they appear to still be referenced in the file... did I need to do something special before I deleted the views... is there some way to clean it up or do I have to start from scratch...?

----------------------- UPDATE ------------------------------------

urgh... okay, this is probably NOT ADVISABLE (especially since I barely know what I'm doing here).

But this is how I've addressed this issue - I really hope there is a better way than this as it was pretty difficult...

I don't really understand "export" and what it does, but it SEEMS similiar to the guidance I've seen here - http://www.sharepointbriefing.com/features/article.php/3935166/Crack-Open-InfoPath-XSN-Files-to-Correct-Errant-Site-References.htm

So I exported the files to my HDD somewhere.

Closed InfoPath completely - it keeps a file lock on the export files/manifest file by the looks of it...

Opened the files and had a hunt around - there was a thumbnail image of a car... weird...
there was a file called manifest.xsf and I opened it in notepad, searched for "dialog" and found many things - so I got notepad++ which highlights reference strings when you double click on them - and found that therer were some "ruleset_N" that weren't IN any related "ruleSetAction ruleSet="ruleSet_"

There were a LOT of these (maybe 20), so I GINGERLY removed them... there were also a handful of these things that don't seem to exist anymore in the form...

 <xsf:unboundControls>
    <xsf:button name="CTRL50_8"></xsf:button>
....

Anyway I removed them, saved the file.

Right clicked on the manifest file and "DESIGN" (or just open from infopath designer)

Then it was much happier and everything seems okay now - publishing "back to the site" appears to work without issue now.

Hope this helps someone - but as I said, there MUST be a better way to do this!? (also I dunno how this file gets into this state, so if you read this and have some advice on how NOT to get this issue in the first place I'm all