-
Oh - that's too bad - in IP 2010 / ShP 2010, I could select my calculated field. I bet if you use an owssvr.dll data connection you'd be able to get the value of your calculated field. Here's some help on that.
-
I've gotten the error about not being able to verify the form template on the server before, but it hasn't blocked me from publishing. What happens when you try to publish? Are errors then returned to the design checker?
-
What about adding a calculated column to the list? You could use that for the description in your drop down.
-
Well. Euw. That makes it seem like owssvr.dll is not going to work w/ your external content list. However, when you connect to the list using a regular SharePoint list data connection, don't you have query fields in the data connection? I do on my ShP site w/ my test external list (see screenshot) - you could just set the query field to the ...
-
Hi - this is what the query fields in the main data source are for - enter your employee number in the query field, run a query on your main data source, and the data for that employee should populate in the data fields. Here's an Office Online article that may help you - Lesson 6 on the page is about querying.
-
Have you checked your SharePoint log file to get more information about the error? C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS is the default location on ShP 2007.
-
Okay - InfoPath doesn't provide anything out of the box for this - but here is one way. You can also do this with qRules, if you aren't up for modifying your form's source files. :-)
-
Hi - do you mean insert a new row? Or set a field's value? Inserting a new row is going to require code (or qRules). You could also include a number of rows in the defaults for the data and hide the blank ones, using some logic to then fill a value and display them...
-
Again - before you try again, that error is usually because of invalid data submitted to the list. Here's another thread with this error.
-
Here's a link to the 4.2 walkthrough, just so you have it. What are the data types of the fields you are submitting to? Are they just text? Lookups, perhaps?