-
You can use substring functions to sort of parse out the date the way you want to see it. I've seen people use secondary data sources w/ special characters in them before to add line breaks - is this a browser form? Or filler? I'm not sure if the line breaks tricks work in browser.
-
Interesting! Does it work in preview (filler)? Do you have the success field on the view you are switching to so you can see its value? Does the same thing happen if you try to set a different field in combination with switching views?
-
Hi - so, when are you setting Success back to false? Another button? Is this the only qRules command you are using? That is - nothing else would be setting it back to true?
You can always post a screenshot under the options tab in a reply to show what the rules look like. :)
-
Oooh - that is pretty cool, thanks for pointing it out! Should work great for non repeating data!
-
Well, I don't think you'll be able to update built in SharePoint columns like "modified by" or "created by". But if you have your own person column, you can do that, the syntax is just sort of special. Here's a link on that.
-
Do you need for users to be able to change this data? If not, you can use an expression box (calculated value) and even leaving the data type as string, display as date formatted. If it is a date data type, you'll need to remove the nil attribute prior to setting the value. Search this article for nil to find the section on how to do that ...
-
The date string you have is a valid date / time for XML - so you could just format the control to display this the way you want to see it (MM/DD/YYYY).
-
Does your form submit just to a SQL database? That is, you don't save the XML anywhere? If so, it may be possible to do what you need w/ very limited or no code, depending on how much work is acceptable for the users. One option would be to use default values for the main data source fields that get their info from the 2ds - if your form ...
-
You can attach them under the Options tab in a reply. It will be later in the day before I'll have time to take a look at this. :)
-
I'd be more interested in the text of the stored proc. Are you setting implicit transactions off in it?