Optimizing iUpdate jobs by updating only the contacts that need changes

Running iDMS iUpdate jobs against large data sets can be time consuming and unnecessary when many records already contain the correct values. It is a best practice to only update the records that actually need to change by using a query to calculate, compare, and filter data before it reaches iDMS.

Rather than updating every contact record, this method does the following:

• Calculates the correct value using a query
• Compares the calculated value to the current value stored in iMIS
• Filters out records where no change is required

The resulting iUpdate job processes fewer records, runs faster, and avoids unnecessary database updates. This approach also creates a clear source of truth for what the data should look like, making the update logic easier to review, test, and maintain over time.

Understanding when to use this approach

This approach is recommended when the following are true:

• A staff user is updating large volumes of records.
• The update value is calculated or derived (for example, based on business rules or multiple fields).
• iUpdate jobs are taking longer than expected.
• A staff user wants to avoid re-updating records that are already correct.
• A staff user needs a more auditable and predictable update process.

👍

Tip

For small, one-time updates or jobs where all records must be updated regardless of current values, this level of filtering may not be necessary.

Creating the necessary components for the iUpdate job

The following components must be created for this process:

1. An IQA group that returns the relevant records
2. A custom business object that exposes the IQA group
3. A query that compares the calculated values and the current values (comparison query)
4. An iUpdate job using the comparison query

Creating the IQA query group

The group created in this step will expose the calculated values as a database view for the business object you will create in step 2.

Do the following to create the IQA query group:

1. Go to RiSE > Intelligent Query Architect.
2. Choose a folder, then click New > Query.
3. Enter a Name.
4. (Sources tab) Choose the desired sources. The source should return every relevant record.
5. (Display tab) Add the following:
   • The iMIS ID or any other unique key
   • From the SQL Expression field, create a calculated field representing what the data should be.
6. Click Run to ensure the data is correct. The results should include the iMIS ID and one or more calculated fields containing the desired end value. This query represents the source of truth for what the data should look like.
7. Click Save.
8. Click the Group tab:
   1. Enter a Group name.
   2. Do not change the Contact key column or Refresh members every settings.
   3. Click Save.

Creating the custom business object using the query group

Do the following to create the custom business object using the query group:

1. Go to RiSE > Business Object Designer.
2. Click New > Design Business Definition.
3. Enter a Name, then click Create Object.
4. Click the Database tab:
   1. From the Tables area, click Add.
   2. Search for and select the query group you just created. The group will appear as a view named similar to vIqa<GroupName>.
   3. From the Available Columns area, select the iMIS ID and the calculated fields from the query, then click Add as Properties.
5. Click Save & Publish. This business object represents the new/calculated data.

Creating the comparison query

The comparison query allows you to compare the calculated values with the current values. This allows you to understand what the values actually are and what they should be.

Do the following to create the comparison query:

1. Go to RiSE > Intelligent Query Architect.
2. Choose a folder, then click New > Query.
3. Enter a Name.
4. (Sources tab) Add the following sources:
   • The standard iMIS source containing the current value.
   • The custom business object you just created that contains the calculated value.
   • Create a relationship between the two sources using the appropriate matching field (typically the iMIS ID).
5. (Filters tab) Add a filter where the current filed value is not equal to the calculated field value:
   1. From the Property drop-down, choose the current property.
   2. From the Comparison drop-down, choose Not Equal.
   3. From the Value drop-down, choose Property, then select the calculated field value.
6. (Display tab) Choose the following properties:

   • iMIS ID

   • The calculated field(s) that iDMS will use to perform the update

   🚧

   Warning

   Confirm the property Alias fields and datatypes match iDMS requirements.

7. (Security tab) Enable Available via the REST API.
8. Save the query.

Creating the iDMS iUpdate job

Create a new iDMS iUpdate job using the comparison query:

1. Navigate to the Cloud Dashboard.
2. Go to iUpdate > New.
3. Create the new job using the comparison query.
4. Configure the remaining update rules as needed.
5. Run or schedule the job. Only the contact records that need updates will be updated.