-
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?
-
In InfoPath, there is no built in rule based way to copy repeating data from a secondary data source to the main data source.
Your options are:
Write code
Use qRules (which is a code DLL you can use with rules)
Use default data and XPath to set default values (this is the only code free option, but involves having a good sense of the ...
-
Hi - so, is the list you are trying to query a survey? Or do you just mean that the questions are in a list?
-
Hi - so they enter a valid token in the form somewhere? You can always have them enter the value in a list data connection query field, then execute the query, then count the returned items - if no items are returned, the token was not valid.
-
Instead of marking the fields as "cannot be blank" you'll have to add custom validation - like:
If field1 = yes and field 2 is blank, display a validation message of Field 2 cannot be blank
It is kind of a pain to set up if there are a lot of fields - but then you have greater control over when a field is required.