I am trying to use Parent child request. The problem is that 1 request(parent) is not account list but departments. The main idea is to get list of departments, and then by department code get accounts for that department. Problem that I am getting empty list of accounts or error in log No account ID.
I think that problem is that first request/response dont have any account information, may it be a problem?
Hi @kskendelis
Did you test this in POSTMAN. If yes were you able to see the list of accounts fetched there?
If you were able to see the response, check for the operation configuration you have made in IIQ Webservice Connector
Hi @kskendelis
Try using Before Rule for getting the list of departments and use configure Aggregation Endpoint to fetch the users from each department. You can leverage the same concept of pagination to traverse through all department endpoints.
I assume the issue is because Parent - Child aggregation will work only for getting additional information on a user.
How often to departments change? It might be a better option to have a rule-runner task pre-fetch the departments and department codes and store them in a custom object, and then load that custom object in your Before rule and use rule-based paging to iterate the departments in a single WSC operation.
You can also look at using the Dynamic Partitioning option to aggregate accounts per department.
Use partitioning to get the list of departments, create dynamic partition(s) (after rule can be used on the Get Partition operation to manipulate the partitions), and aggregate account(s) with the Partitioned Account Aggregation operation(s). Enable Partitioning option on the Account Aggregation Task.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.