-
The dateTime you are receiving back has a shift for time zone:
2004-10-04T00:00:00.0000000-04:00
If you want the current dateTime, not accounting for a time zone, you need to grab the first 19 characters:
2004-10-04T00:00:00
Perhaps the Web service can be configured to return a dateTime without the time zone. If not you can use code to fix ...
-
You need to use the XML Object Model and XPath to access your values. You have a field to which the drop-down list is bound. That field holds the selected value of the drop-down list.
So you would do something like:
XDocument.DOM.selectSingleNode(''/my:myFields/my:DropDown1'').text
Greg Collins [InfoPath MVP]
-
I'm not much of a SQL person yet, and I'm assuming you are using SQL to store these 130,000 records.
But it seems to me that if you have the beginning number and ending number for the range you want that you should be able to build your query in code and then call the Query() method to retrieve your records.
I.E. query = * WHERE CASE >= TEXT1 ...
-
Please provide more details. I don't understand what you mean by ''query between two text boxes''.
Greg Collins [InfoPath MVP]
-
Cool! Glad you got it worked out!
Greg Collins [InfoPath MVP]
-
I'm glad your main issue was fixed. Without more details I doubt I can help on the error message you are receiving.
Greg Collins [InfoPath MVP]
-
If you have your Web service established as a Data Connection, then the schema has already been created and is part of the .xsn file. If you extract the form files (See the File menu in the designer), then you can see what .xsd files are in your template.
Again, if you have the Web service as a Data Connection, then the schema is present and you ...
-
Will you post your filters here? Select ''The Expression'' in the first drop-down list and then copy the results from the text box that appears after it. Its likely just that one of the filters are missing something.
Greg Collins [InfoPath MVP]
-
I'm assuming you have some sort of a relational item that connects features to solutions. If this is the case, you can add a filter on the repeating section for the features that only shows features that relate to the solution.
Did that make sense?
Greg Collins [InfoPath MVP]
-
Saving to XML is nothing more than File | Save. Anyway, you found out that your fields did not exist... so this appears to be your problem.
To learn about Optional fields, please refer to the InfoPathDev.com Dev Nugget titled, ''The Difference Between Optional and Not Required'', which can be found ...