Workflow to trigger unoptimized aggregation

I am trying to create a workflow to trigger an unoptimized aggregation on a source. We are currently doing that manually and if i can automate it i would rather do that.

it’s a cc API
https://promedica.api.identitynow.com/cc/api/source/loadAccounts/17647 where 17647 is the SourceID.

I am getting an error that says “unable to ensure name is unique” it’s happening on the HTTP Request step i believe.

Hi Scott. Can you share a screenshot of the error message and the JSON body you used in the HTTP request?

I can’t save it so i can give you the JSON body. The error appears when you try and save it.

Here are the contents of each box on the HTTP Request form
Description

triggers an unoptimized aggregations for GHR Work assignments

auth type - oauth

token url -https://promedica.api.identitynow.com/oauth/token

client ID - using the Client ID i generated before

secret - using the secrete i generated before

credential location - header

scope - blank

request url - https://promedica.api.identitynow.com/cc/api/source/loadAccounts/17647

query parameters - none

request headers - none

method - post

request Content type- form
disableOptimization true

The workflow is a scheduled trigger > HTTP Request > End Step.

I can save just the scheduled trigger and end step if you want to see the JSON for that.

Unoptimized Aggregation Workflow.json (2.7 KB)
Here is an example that triggers the aggregation. It also sends an email just for testing but that can be removed.

Replace the tenant, sourceID(s) and add the client ID and Secret.

4 Likes

Thanks Edward I will take a look at this.

I wanted to say thanks. Your workflow has been working fine. I still need to compare yours and mine to find out what i was doing wrong.

Thanks again for the assist!!

2 Likes

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.