-
My guess is that it's not the browser, but rather the browser security settings. I use only IE7 and IE8, and this web service is in every form I build. It works in IE 6-8 with no problems, so at least with knowing that info, it should be easier to troubleshoot. I'd start by checking the zone settings on those browsers to ...
-
Ok, totally fine if you want code in the form, but it's best to avoid code unless absolutely necessary. I make all of my forms without code unless they have qRules in them. :)
-
InfoPath Forms Services - the tool for browser-enabling InfoPath forms - is only available in SharePoint (MOSS) Enterprise. You can't do this without SharePoint.
To use InfoPath full client, you can't do that either for non-Windows, because it requires each user to have InfoPath installed, which is an Office product requiring ...
-
There is no search feature in InfoPath, and search results in SP are not hard to read. What got you afraid of SharePoint search? It is a very robust search engine that can do tons of things if you configure it properly. Think about it - the SharePoint team puts tons of time and money into the SP search engine while InfoPath has ...
-
You can't dynamically populate OOTB workflows, but you could very easily make your own approval workflow in SharePoint Designer 2007. Just promote the fields of your form to the form library during the publish process, and then use the SPD workflow to notify the relevant parties at the correct time.
In your form, use conditional ...
-
Yeah, you can't just copy a form over - it has to be associated with the same form template in the next place.
What requirements makes you have to copy the XML file elsewhere?
-
Hmm, shoot, I am not sure which data types aren't supported. I'm surprised number type fields are like that.
Anyway, the first method is a best practice, because it's much better to create site columns (even site collection columns) so that the same column can be re-used in other places on your site (or site collection). ...
-
Security restrictions are way different for a browser form than a rich client form, which is why it works in Preview mode (rich client) but not in browser mode.
We've had this same question several times recently on multiple forums, and unfortunately it is just not a straightforward thing to resolve. Qdabra created their DBXL tool ...
-
You can create the column in SharePoint first and make it the data type you prefer, then you when you promote your field, associate it with the pre-made column in SharePoint.
Or, you can select the button at promotion time that says "allow users to edit in SharePoint." If you do that, then the column name in SharePoint becomes ...
-
Great! Glad it worked out. Other than starting from scratch, was there anything you did different that made it work? In your workflow, did you use set field in current item or update list item?