We are have deployed an Epic EMP connector to the production IDN tenant for our client and we are getting the error depicted in the following screenshot during entitlement aggregation:
Account aggregation completes without error, only entitlement aggregation is failing. This aggregation also works in the sandbox environment with the same entitlement types and entitlement schema configured. As an additional test, we have tried making another Epic EMP connector with all entitlement types removed except for group. When running entitlement aggregation on this second connector, the error on linkedSubtemplate no longer occurs, but the first error remains:
We have also tried looking into the connector logs to confirm outbound API request used by the connector when retrieving entitlements, but we could not confirm this information from the logs. From Postman, we tested the following API call that we believe should return Epic EMP templates:
However, the response for this request returns user records instead of templates. Could someone assist with this entitlement aggregation error or provide any insight on configuring the Epic EMP API request to get templates for troubleshooting the error?
Hello, I’m not sure if you’ve been able to mitigate these errors yet but I’ve found a way to temporarily get it working. I’m not sure if it is placebo or not, but I’ve modified the Aggregation settings in our Epic EMP connector. This is what I’ve set:
Page size: 150
Timeout: 1800
Partition Aggregation: On
Number of Partitions: 10
This is all happening because of the way this connector has to work. It appears like it does a request for all EMPs, then it goes through each page and does individual requests for information on each ID it gets. After it has done that it then processes that data. This is what lead me to think that lowering page size and increasing time out would help. So far our Production environment hasn’t errored with these settings, but our Sandbox environment is still hit or miss.
GetRecords will just grab the list of users as Stephen suggested.
After that it has to pass on a list to each thread to gather the real data via ViewUser. Unless they found another API, you have to do ViewUser to get the assignments of Templates (Linked and Subtemplate) to the User.
I cannot find another API call that would just return template assignments.
