Hey, everybody. I have a problem with the API and calendars.
The main question is: Is it possible to change the description in calendar events with preserving the formatting.
1 - Through DAS - the description field does not have any formatting. Accordingly, there is no possibility to change the description without losing the formatting.
2 - Via REST API - it’s more complicated here, when receiving an appointment, it has an incorrect start time. When trying to change it, the appointment changes its type to 4 = Reminder. And when making a PUT request, formatting is not applied even if descriptionContentType = text\html is specified.
Are there any knowledgeable people who can help with this problem?
**I have server 14.0FP4 and REST API 1.1.3.1 installed
Hi. No one knows the answer or no one understands what the problem is? Maybe you need more details?
Can you give more details via Domino REST API? Please give example of the endpoints being called to create (if you are doing a create via DRAPI) and doing the update, please include the endpoint as well as the body being sent and we can take a look at it.
Yeah, sure. Here’s what happens when working through Rest API 1.1.3.1.
1 - A meeting is created via Verse. The appointment after co-creation looks like this:
2 - There are 3 variables in Postman:
3 - Using the “pim” query I get the encounter.
REST - {{HOST}}/pim-v1/calendar/default/{{CAL_UNID}}:
4 - Now I need to change the description while keeping the formatting intact. REST - {{{HOST}}/pim-v1/calendar/default/{{CAL_UNID}}:
5 - The change request is working, BUT the appointment has now changed view and the description has broken formatting:
What is the problem and how to deal with it? Please help me to understand )))
Hi. I’ve added a description. Did you get a chance to read it?
Hello. Do you have a possibility to check the problem?
Hi @Aleksandr , yes, you are correct, that appears to be broken. I believe the original intent was to use MIME for PIM, but where the get returns HTML, you should be able to put it back as HTML.
I will create a ticket to resolve this in the next release (the version following v1.1.4 as that is in the queue to be released soon).
Thank you,
Ron
1 Like
That’s great. I’ll wait for 1.1.4. Thanks.
Sorry, no, the next version, most likely named v1.1.5.
1 Like
