-
Do you mean even when the user types in the field, you can't see the data? Maybe attach a screenshot under the options tab in a reply to help us understand. :)
-
If you publish a form to a library, you can add a form web part to a web part page and then display the form in a web part - does that work for you?
-
Hmmm. So - your forms are moved - but they would still be linked to their original template (that is just the way InfoPath is) unless you relink them - is the new library on the same site? It sounds like when you try to open the moved forms they try to open in filler instead of the browser.
-
We do have functions in qRules that will help in an admin deployed template. You might also want to check out another of our products - DBXL has a ton of web services that work well in the browser and can query and submit SQL data.
-
Oh, got it - yah, I didn't understand the issue. Your approach is correct - using different namespaces lets you have same named groups with different fields.
-
So - was there a rule that caused this? It wasn't just some design checker weirdness?
-
I think you'd need to use references for the individual fields for something like this - so you'd create the groups, add fields you need to one group, and if you need the same named fields in your second group, you'd right click the field you created, select reference, and then select the other group....
-
Given the simplicity of the form, the first thing I'd guess is that either the SharePoint server doesn't have the sandbox service configured, OR you are not a site collection admin. Can you check those things?
-
Oh. Your repeating table is a secondary data source. Your hyperlink is bound to a field in your main data source. You'll see on the control a message that the control can't correctly repeat in its current location. Your secondary data connection uses DBXL - are you querying a SQL table or a view? Personally - I would query a SQL view and ...
-
I'd go with sections since view switching is having a fit - actually, I'd probably test the 2 view switches in the browser first (with both in code) just to see if the form behaves differently in the browser. :)