InfoPath Dev

I am trying to create an appointment in the calendar using this command. I am getting an error that says "Errors occurred submitting to list: Invalid date/time value. A date/time field contains invalid data. Please check the value and try again.". I am simply using a date picker control with time. Can this be done or do I need to try and use a workflow?

I wonder if it might be a formatting issue. The SharePoint calendar list might want the date/time to look like this (and perhaps InfoPath is not matching exactly the format):

Yes, my first thought as well. Don't know how to include a pic in this forum, but I did adjust the format to match the add event format and am getting the same error.

 We're investigating. More soon...

Indeed, the SharePoint calendar does not like the date/time format. Hilary has come up with a nifty workaround: using FormatDate to set the dates to "u" format, meaning that now they'll have Z at the end. SharePoint seems to like this format. Here's the command:

concat("FormatDate /date=", <datefieldhere>, " /format=u")

I'm attaching a sample form which you can look at in design mode. Let us know if you run into any questions!

Thank you for the example file, that helped alot. I am now getting the appointment created on the correct date, but the time is showing as 12:00:00 am regardless of what I use. Did that happen for you?

Oh, interesting! My multi day appts. get created at the right time, but the ones that start / end on the same day do not...

But, if I add a "T" between the date and the time - they get created at the right time...

There's a lot to be said for brute force. Try this for your format date:

/format=yyyy-MM-ddTHH:mm:ssZ

Works nicely for me....

OK, I'll try that right away.

How did you manage to sneak the 'T' into the formula?

I changed my /format parameter for my format date command - see attached. The rules are on Start Date and End Date - I'm using a custom format for /format.

Working!!!  Thank you very much.

Cam

Wonderful - thanks for your patience. It takes a little figuring sometimes to know what SharePoint expects - I think it is only Calendar lists that expect this format, I'm pretty sure we have tested date time data types with custom lists and not run into this issue.