Account aggregation not working when Partition enabled

IdentityIQ (IIQ) IIQ Discussion and Questions
1

Which IIQ version are you inquiring about?

8.4p3

Please share any images or screenshots, if relevant.

Error : An error occurred while attempting to create task partitions for Application: Ensure that you have defined valid partitions in order to leverage Partitioned Aggregation for : account,Azure AD.

Please share any other relevant files that may be required (for example, logs).

NA

Share all details about your problem, including any error messages you may have received.

Account aggregation was working with partition before we upgraded from 8.3P4 to 8.4P3

2

The connector documentation describes in detail how to setup the partition filters.

Do you have “userPartitions” defined in your application object? For example:

      <entry key="userPartitions">
        <value>
          <List>
            <!-- digits -->
            <String>startswith(immutableId,'1') or startswith(immutableId,'2')</String>
            <String>startswith(immutableId,'3') or startswith(immutableId,'4')</String>
            <String>startswith(immutableId,'5') or startswith(immutableId,'6')</String>
            <String>startswith(immutableId,'7') or startswith(immutableId,'8')</String>
            <String>startswith(immutableId,'9') or startswith(immutableId,'0')</String>

            <!-- letters, these filters are case-sensitive -->
            <String>startswith(immutableId,'a') or startswith(immutableId,'b')</String>
            <String>startswith(immutableId,'c') or startswith(immutableId,'d')</String>
            <String>startswith(immutableId,'e') or startswith(immutableId,'f')</String>
            <String>startswith(immutableId,'g') or startswith(immutableId,'h')</String>
            <String>startswith(immutableId,'i') or startswith(immutableId,'j')</String>
            <String>startswith(immutableId,'k') or startswith(immutableId,'l')</String>
            <String>startswith(immutableId,'m') or startswith(immutableId,'n')</String>
            <String>startswith(immutableId,'o') or startswith(immutableId,'p')</String>
            <String>startswith(immutableId,'q') or startswith(immutableId,'r')</String>
            <String>startswith(immutableId,'s') or startswith(immutableId,'t')</String>
            <String>startswith(immutableId,'u') or startswith(immutableId,'v')</String>
            <String>startswith(immutableId,'w') or startswith(immutableId,'x')</String>
            <String>startswith(immutableId,'y') or startswith(immutableId,'z')</String>

            <!-- letters, these filters are case-sensitive -->
            <String>startswith(immutableId,'A') or startswith(immutableId,'B')</String>
            <String>startswith(immutableId,'C') or startswith(immutableId,'D')</String>
            <String>startswith(immutableId,'E') or startswith(immutableId,'F')</String>
            <String>startswith(immutableId,'G') or startswith(immutableId,'H')</String>
            <String>startswith(immutableId,'I') or startswith(immutableId,'J')</String>
            <String>startswith(immutableId,'K') or startswith(immutableId,'L')</String>
            <String>startswith(immutableId,'M') or startswith(immutableId,'N')</String>
            <String>startswith(immutableId,'O') or startswith(immutableId,'P')</String>
            <String>startswith(immutableId,'Q') or startswith(immutableId,'R')</String>
            <String>startswith(immutableId,'S') or startswith(immutableId,'T')</String>
            <String>startswith(immutableId,'U') or startswith(immutableId,'V')</String>
            <String>startswith(immutableId,'W') or startswith(immutableId,'X')</String>
            <String>startswith(immutableId,'Y') or startswith(immutableId,'Z')</String>

            <!-- special chars. we do not check for = since that is used as padding on end -->
            <String>startswith(immutableId,'+') or startswith(immutableId,'/')</String>
          </List>
        </value>
      </entry>
3

hi @mayamis1703eq

It looks like the upgrade from 8.3p4 to 8.4p3 introduced a change in how partitioned aggregation validates partition definitions. The error usually appears when IIQ can’t match the partition config to the application schema after the upgrade.

A few things you can double‑check:

  • Make sure the partition attributes (like partitionColumn, partitionValues, etc.) still align with the current Azure AD schema in 8.4p3. Some attribute names changed between versions.
  • Re‑save the application and partitions — IIQ sometimes needs a fresh compile after an upgrade.
  • Confirm that the partition definitions exist for all object types you’re aggregating (e.g., accounts, groups). Missing one can trigger this error.
  • If you customized the Azure AD connector before, the upgrade may have overwritten or altered parts of the XML. Comparing the old and new connector XML often helps.

Since it worked before the upgrade, this is most likely a schema or config mismatch rather than a functional issue with partitioning itself.