I am working on a connection with a source that currently has Account Aggregation working. I can run an API with the same API and APP token information and it does return the following using this JSON path ($.data[*].attributes.name):
[
“Example Admin Role”,
“Example Read Only Role”,
“Example Standard Role”,
“Standard Role plus Monitors”
]
I have that JSON path set as a response mapping for the entitlement ID and Name, however my entitlement aggregation is showing success with 0 objects scanned. I’m not sure what I’m missing on this or if there is more information that is needed. Please let me know what other information is needed or what I’m missing.
Thanks!
Michael
Please be sure you’ve read the docs and API specs before asking for help. Also, please be sure you’ve searched the forum for your answer before you create a new topic.
Please consider addressing the following when creating your topic:
What have you tried?
What errors did you face (share screenshots)?
Share the details of your efforts (code / search query, workflow json etc.)?
What is the result you are getting and what were you expecting?
Thank you for the clarifying questions. This is a web services connector utilizing API key authentication. Not a custom connector. I do have a group aggregation HHTP Operation setup.
Headers are the API and APP key. Body is Raw and empty. Response Mapping is set with the JSON path in my initial post on the right and the matching name of a configured Entitlement on the left.
When I do the GET api call in that same exact URL (Base plus Context in screenshot) I get results.
Here is a screenshot of the entitlement type. Yes, I performed the test in postman, the results are pretty huge but the JSON path that I posted returns those 4 results. Those are what I’m hoping to bring into ISC for provisioning and deprovisioning.
Ok I think the issue is you need to put the JSON path in the response information section, and just the attribute name in the response mapping. So under the response information section, put:
$.data[*].attributes
Under root path (and make sure to include the response success code such as 200 or 201 depending on what the API returns)
Under the response mapping you should map access_role to name
I updated the response path here to also be $.data[*].attributes.name, there is no response mapping on that though. Maybe that operation is redundant, but I still got 0 object scanned after making the updates. Here are screenshots of the group aggregation operation to make sure I understood you right.
I was able to find the issue. The full json path $.data[*].attributes.name was too much in response information. taking off .name and then adding $.name to response mapping worked. Which is what your response was saying Vincent. Thank you so much for your help.
Please be sure you’ve read the docs and API specs before asking for help. Also, please be sure you’ve searched the forum for your answer before you create a new topic.
