-
Well, the syntax is where ColumnName like '%value%', so, in general, this looks correct. Can you open SQL Management Studio and try to execute your query with a where clause and the value you are trying for last name and see what your results are?
-
I'm used to 1 = true, 0 = false, but still, I tried a sample form set up like this and it worked as anticipated in the browser (InfoPath & SharePoint 2010). If I were troubleshooting this, I would probably put a text box on the form bound to the field to see what the actual value is. I'd check the default value for the field. I might ...
-
You should just be able to set the element and attribute to blank in code. Here's an MSDN article that may be helpful.
-
You may want to consider a web service (we sell an awesome one here) or something like qRules that would allow you to filter your SQL query without having to write code yourself.
-
For IP 2010, where you can add a hyperlink control, it is bound to an element (which holds the url) and an attribute (which holds the display text) - I'd assume you'd need to set both of those to blank with a rule to clear the control correctly.
-
If you add code to your button, you should be able to use something like this to get the purpose:
e.Source.selectSingleNode("ns1:Purpose")
Run in debug on the event on the button so you can look at e.Source. :-)
-
In an on before change, the DOM is read only - you need to run your code in a changed event.
I feel like I'm not explaining well - and I am kind of at a loss as to how to explain better - I'd hoped the sample form would help. The thing is that your PurposeCategory data source only has the items for the second purpose when you query it ...
-
[quote user="joanfuture"]Well, I understand this workaround. But there must be something going on with synching RichText. When I look at the version list for an item, Richtext is always submitted, whereas other Fields such as Title or Due Date, they are only updated when they are actually changed. [/quote]
So - I have a form mapped to ...
-
I may be a little confused too - when we refresh, we compile a list of all the items that are in the XML that have a SharePoint ID - so we know which ones are removed from the XML while the form is in use, and can delete on submit.
But, looking back at your original post, I believe you and Jimmy have had some email exchanges on some other issues ...
-
Hey, Jerry - last I heard was an email on Monday that they were still investigating - I'll ping the contact I've been dealing with later today.