-
Which view(s) are you having an issue with? Can you attach a screenshot that shows the issue?
-
Probably in your data connection that returns addresses, you have it set to run on load. So, when the form opens, the data source is queried and returns all the items.
Under data connections, select the one with the issue and select modify. In the last dialog for the data connection there is a checkbox for setting it to run when the form opens. ...
-
That seems very strange. Can you check the postback settings on the button? Right click the button and under the properties, check the browser tab. Perhaps try setting postback to "always" and see if that helps?
-
Hi - if you want, you can attach your form under the Options tab, and I'll take a look and see if I can find anything that seems odd / incorrect.
-
How are you naming the forms when they submit? If you use something unique for the form name (like a field that you can set one time to the functions now() and userName()) does that solve the issue? It sounds like you may have one user overwriting the other.
-
No, each drop down has to be set up individually, I'm afraid - even though they can all use the same list for their data.
-
Oh dear - this sounds like a pretty yucky bug. Are all the users using the same version of IE? Everyone have the same Windows / Office updates installed? Maybe try clearing the template from the cache and see if they can open it w/out it crashing? Not all users are having this issue?
-
Hi, Ed - this is the one you found the answer to, right? It had to do with how the URL was entered into the dashboard? I think in your other post you said you needed to encode the spaces?
-
Secondary data connection fields (query or data) won't retain values when the form is closed and re-opened. You can add some Form Load rules to set your query fields and re-execute your query.
-
Have you tried with setting the qRules "useWebServices" to true? The code is slightly different between filler and browser forms - so if everything works when you test it (in preview, I'm guessing?) then maybe emulating that in the browser will prevent this from happening?