0bp9x (0bp9x) asked a question.
Hello! I'm working with the CVENT api, and one necessary key in the body is "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User": {
"sendLoginDetails": true
}
The problem I'm running into is that when the entire body object is formed, the key displays exactly as-is. By the time the PUT request is executed, the key changes to:
{
"urn:ietf:params:scim:schemas:extension:enterprise:2": {
"0:User": {
"sendLoginDetails": true
}
}
When naming the attribute/key in the Object Construct, how can I escape the period so it doesn't split the key into 2 pieces as it did above? I've tried using both of these encoded strings as the Object Construct attribute name:
urn%3Aietf%3Aparams%3Ascim%3Aschemas%3Aextension%3Aenterprise%3A2%2E0%3AUser
"urn%3Aietf%3Aparams%3Ascim%3Aschemas%3Aextension%3Aenterprise%3A2%2E0%3AUser"
And neither fixed the issue (still get a 500 response error indicating the key is wrong)
is it a Default api for Default okta workflow connect? or parse it by json function in okta workflow?
@0bp9x (0bp9x) -- I do remember running into this at some point in the past. I think there might already be a defect around it.
However, to meet your needs leverage a compose + JSON parse.
Keep in mind Compose can be dynamically set also. So if the object you are building is following some schema and you have dynamic properties those can be fed dynamically into the compose then converted into a type:object using JSON parse.
@TimL.58332 (Workflows) Thank you! Out of curiosity though, how would I go about handling multiple objects within the list? I'm performing a PUT call with data, and values omitted will result in the user losing information
@0bp9x (0bp9x)
I am not entirely sure what you are asking. You essentially build out the schema you want then drop in the values dynamically. This is basically what you have to do when working with an API that only leverages XML and is a workaround in this scenario.
There is a "Stringify" card available that can convert lists/objects to strings that can be then fed into a Compose card.
Here's an example expanding on what i showed previously.
Output:
{
"mainList": [
"val1",
"val2",
"val3"
],
"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User": {
"sendLoginDetails": true
}
}