I have been experimenting with the REST APIs and Date/Time fields. I am POSTing to an Import Set and then GETing from the corresponding table. When we post, we are posting all Date/Times in 'GMT', but for the longest time I couldn't figure out wh...
I am trying to set up a successful POST REST call to the ImportSet API. However, I think I have my user permissions mixed up and I don't know how to sort them out. When I post as a user with admin permissions, the record is successfully created...
::sigh:: and as an addendum, something seems to be buggy here even more than the unknown transform happening on import. This morning, when I was testing with the user's timezone set to GMT, it was getting imported as exactly 12 hours ago. Now (3 ...
Hmmm...well, the default value for sysparm_display_value is false and we are not changing it. So maybe the weirdness is on import to the update set? I am positive that we are always sending the date/time in UTC. I've checked the payloads while ...
Thank you for your suggestions, Peter. The first suggestion is what we are currently doing. While it does work, it's not really ideal. Our end goal is to provide the application with data controlled by varying roles, but have the user set up what...
Srinivas Thelu It appears that having both import_set_loader and import_transformer roles allow the request to go through and the proper response to be given in return! It still seems strange behavior that I've witnessed and not all together intuitiv...
I do have a table level ACL defined for that user's role...all CRUD operations allowed. I did not define individual field level controls, because I don't care to be that specific. The wiki page you posted seems to indicate that if no field ACL ex...
