-
I'd put some breakpoints in the code and run in debug so you can check the errorNav and the outputNav. Here's some help on how to do that in case you need it.
-
The code in your post won't actually compile, will it? You are using inputNav, etc prior to actually executing the connection?
-
Hi - I updated the sample form to show this. I changed the fields to a date datatype, and changed the format of the original data so it was correct for XML dates (yyyy-MM-dd).The rule is on field1 & sets field2 to the rate. It was a little counter-intuitive for me - we want the row where the start date is less than the selected date and the ...
-
Perfect, glad you got it squared away!
-
When you set the value of the EMMAStartDate in your form, you could try using the translate function to replace a blank space character with T -
translate(fieldname, " ", "T")
Your destination list data type would need to be Date for you to get a formatted value displayed.
-
Can you please, please, pretty please tell me what the data types are in your destination list? Are they both date? Are they text?
So you know, in XML, you'll need a T between the date and the time for it to be considered a valid XML date/time value:
yyyy-MM-ddThh:mm:ss
-
I was actually wondering about the data types in the final list that you are writing to with SubmitToSharePointList, not the form. Does that make sense? The bottom picture in your screenshot refers to your destination list - I'm wondering about the data types for the columns in that list.
-
So - you are all set? That's great news!
-
In your SharePoint list, what are the data types for EMMAStart and BirthDate?
-
Hi - so, I think you are saying that when you populate dates in your form from the SharePoint list and then submit that data back to SharePoint (using qRules), the list doesn't display the dates correctly? Can you attach a screenshot (under the Options tab in a Reply, you can add a file) to show me the issue so I understand a littel better?