InfoPath 2010 Design Checker dialog box error - InfoPath Dev
in

InfoPath Dev

InfoPath 2010 Design Checker dialog box error

Last post 10-04-2012 08:20 AM by Hilary Stoupa. 2 replies.
Page 1 of 1 (3 items)
Sort Posts: Previous Next
  • 10-03-2012 06:27 PM

    InfoPath 2010 Design Checker dialog box error

    InfoPath 2010 design checker throws the following error "Dialog box actions are not supported". When I click on the error I receive the following pop up message: "Using a rule to automatically display a diaolog box is not supported in web browser forms..." Problem is that it doesn't show where on my form I have a dialog box action. I've manually checked all my data sources / fields and I can't seem to find it... I wish I could upload the XSN template, but I am about 100% certain that my organization would not be thrilled about that. Any suggestions?
  • 10-03-2012 06:50 PM In reply to

    Re: InfoPath 2010 Design Checker dialog box error

    Ok so I just solved it... Lol!! Here's how I solved it: did a "Save As" and spun off a second copy of the form. Closed the original, opened the new one (just to be 100% certain). Now I started deleting. I deleted all the form views and then ran the design checker again. Didn't do it; then I deleted almost all of the data sources - that fixed it! (Surprise? Not really). Closed the mangled version without saving. Then I reopened it and deleted about half of my data sources; the second half eliminated the error. Close without save and reopen. Did that about 3 or 4 times, deleting and running the design checker. Finally found the suspect field. As it turns out, I had a dialog box rule for a field, but I had disabled that rule at some point during the design process. Perhaps this is why it didn't take me to the suspect field? After finding the suspect rule I then reopened the original form and deleted it, solving the problem. So there it is, problem solved.
  • 10-04-2012 08:20 AM In reply to

    Re: InfoPath 2010 Design Checker dialog box error

    Another option might be to save the form as source files and search the manifest.xsf - not sure what the action is for a dialog box, but you could make a little sample form with just a dialog box rule, save as source files, and look at the manifest.xsf - then you'd know what to search for. :-)

    I do this when I accidentally break forms by removing data sources they are using someplace.

    Hilary Stoupa

Page 1 of 1 (3 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.