-
I don't believe so, but that's also not the problem. It's the way SharePoint is displaying it that's the problem and that's probably where to look.
-
Hello Rachael and sorry for taking a while to respond.
Unfortunately, the InfoPath designer doesn't provide any features for adding and removing rows from repeating sections. If you want to do so, your two options are to (1) write your own custom code, or (2) use a framework like qRules, which is based off of code, but abstracts ...
-
Have you tried selecting a different date format under the TextBox's formatting options? I don't know if anything can be done about the SharePoint library. The date is stored as a standard XML date regardless of how it's formatted, so the library's settings might be the place to look if it can be done.
-
How's this?
http://www.infopathdev.com/forums/p/8953/31786.aspx#31786
-
The dfs namespace url was right the way it was before. That shouldn't be changed. And as I pointed out previously, it appears that this path is missing a whole bunch of pieces between dfs:dataFields and Product notes, and you also need to add the d: prefix before ProductNotes, ProductNote, ...
-
It looks like beneath dfs:dataFields, you have GetProductsNoteResponse, GetProductsNodeResult, ProductNotes, and then ProductNote, and these all have the namespace http://thomsonlearning.ecomm.orca.com, so you need to assign a namespace prefix to that url in the selection namespaces and use that in the XPath.
-
Why not just use today() in your conditional formatting instead of storing it in a field? Alternatively, you can use a Form Load rule to set that field to today() when the form is opened.
-
This should work:
IAVA1_CD <= addDays(today(), 7)
You might need to finagle the logic to get it to work with your other conditions.
-
To the best of my knowledge, SharePoint promoted columns always use DateTime rather than just Date or Time. I don't know much about SharePoint's internals, but my guess would be that it's because SharePoint also uses an SQL Server DateTime column to store the data.
So I don't think there's a way around having ...
-
You should be able to accomplish this with an expression like this:
Condition:
Expression: /path/to/repeating/group[Disapproved = 'true' and ReasonForDisapproval = '']
Disable the control