Grant Cooper
My feedback
1 result found
-
1 vote
An error occurred while saving the comment An error occurred while saving the comment Grant Cooper
commented
Another update.
I am passing this event dictionary (using Python language) to my create_event function.
event = {
"Name": "Test Event 8",
"EventType": "RSVP",
"StartDate": "2022-10-15",
"StartTimeSpecified": False,
"EndDate": "2022-10-15",
"EndTimeSpecified": False,
"Location": "Quail Creek, St George Utah",
"RegistrationEnabled": False,
"Tags": [
"rockies",
"local series"
],
"Details": {
"DescriptionHtml": "A fun family event",
"TimeZone": {
"ZoneId": "Mountain Standard Time",
"Name": "(UTC-06:00) Salt Lake City",
"UtcOffset": 360
},
"AccessControl": {
"AccessLevel": "Public"
},
}
}My event is being created and now shows the correct time zone, however the start date in the web interface is still 1 day earlier than I set in my POST request via the API.
We can see in the dictionary snippet above the StartDate is "2022-10-15", but in the attached screen capture the web interface shows October 14th.
How do I set this correctly ?
An error occurred while saving the comment Grant Cooper
commented
As an update, t seems I have resolved the sessions StartDate issue. I had simply copied the payload from the Swagger API example and if "sessions" is included then it must be set. I deleted that section entirely from my payload of the POST command and it the create_event call still worked successfully.
The setting of the Event=> Details => TimeZone is still an issue however.
Grant Cooper
shared this idea
·
Thank you Vassily Kholopov,
I had tried using ISO8601 format and that was successful.
I just now also tried your suggestion of simply including an offset and that also worked.
This has solved my question.