If I replace the end date with "2024-06-13T00:00:00.000Z" (json = {'op': 'replace', 'path': '/deadline', 'value': '2024-06-13T00:00:00.000Z'}), the api saves the data like this: "2024-06-13T00:00Z"
However, if I replace it with "2024-06-13T00:00:00.001Z", the data is stored in this format.
This causes me problems when I read the data from v3/campaigns/:id, as the format is not always the same (requiring additional controls).
I don't know whether it's the data format that's wrong when saving (update) or when reading (get-campaign).
Hello,
I found a surprising behavior on this endpoint:
If I replace the end date with "2024-06-13T00:00:00.000Z" (json = {'op': 'replace', 'path': '/deadline', 'value': '2024-06-13T00:00:00.000Z'}), the api saves the data like this: "2024-06-13T00:00Z"![image](https://github.com/sailpoint-oss/developer.sailpoint.com/assets/90192744/2c620281-9c2c-497c-bcbe-1dd55413bae2)
However, if I replace it with "2024-06-13T00:00:00.001Z", the data is stored in this format.![image](https://github.com/sailpoint-oss/developer.sailpoint.com/assets/90192744/1d618a5e-b0bd-42f2-b5de-69ae19a1d44b)
This causes me problems when I read the data from v3/campaigns/:id, as the format is not always the same (requiring additional controls).
I don't know whether it's the data format that's wrong when saving (update) or when reading (get-campaign).
Have a good day, Thomas