-
So - you are saying you don't think your conditional formatting is working correctly, I think - that you are hiding each field? Wouldn't you just put the fields in a section and hide the section? Can you attach your form under the Options tab in a reply so I can take a look & maybe understand the issue a little better?
-
Save your form as source files (from the Publish menu, Export Source Files) - template.xml will have everything included by default - if you have some fields or sections that are optional, check sampledata.xml. The schema files will also be there, of course, so you can investigate that as well.
-
I haven't - I haven't worked w/ linked tables in Access much, like maybe once or twice - can you just create a new DB that has the linked table & see if it reproduces?
-
That error is one I usually see when a form hasn't been published correctly. Did you publish the form? You may want to try using a site content type - but the user is still going to need to be able to write to the library in order to submit.
-
What does "don't go away" mean? The fields don't hide correctly? Or you were expecting the field values to clear? You may need to add rules to clear the fields - so, on question 1, have a rule that clears these fields, then have the logic that if question 1 = A, reset the fields accordingly. Does that make sense?
-
So - you just need to disable the button if you have two items that match? See if the attached sample helps you at all - save locally, right click and select design, then preview so you can try it. PS > as to the spacing issue, I'm finding that IE works best for the forum. What browser are you using? I'm using Edge right now and it just ...
-
No, sorry if I was unclear. Out of the box in InfoPath, the error will display. You can add code (or use qRules) to execute the query and handle for errors that way.
-
How interesting. And this is just a regular email submit connection? And a regular InfoPath form published to a SharePoint Library? Any chance I can see the form?
-
I don't have good news - out of the box, if the query fails, InfoPath is going to return an error message to the user. Did you develop the SOAP web service (I'm assuming that is what you mean by SOAP database)? Maybe the web service could be modified to just take user name and not include domain? Then you could use a substring-after ...
-
I've actually never seen the behavior you describe - only that of the other users, where the email prompt comes from InfoPath and the user can't edit anything. Can you attach a screenshot of the behavior you see? You can attach a file under the Options tab in a reply.