Db and UI out of sync

IdentityIQ (IIQ) IIQ Discussion and Questions
1

Which IIQ version are you inquiring about?

8.4p1

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

Hello, I have several instances where I update an object programatically but it does not get updated in the backend.
I updated extended attribute of a managedAttribute and it did not get updated in the db. Today, I updated the proxy of an application and it also did not get updated in the db. could there be a reason why this is happening?

2

@dmaan
Looks like some issue with your HBM file configurations and Object config mapping, please share those once and recheck at your end

There is no way UI having one value and db having other unless both the fields are not mapped correctly

Also please check the objects in debug page as well once.

3

Hi @dmaan,

There are a few reasons why your updates might not be persisting in the database. Here are some things to check:

Are you committing the changes?
After making modifications to an object, you need to explicitly save and commit it. Try using:

context.saveObject(managedAttribute);  
context.commitTransaction();

If commitTransaction() is not called, the changes may not be persisted in the database.

Check for caching issues
Sometimes, IdentityIQ caches objects in memory, and updates may not be reflected immediately. Try calling:

context.decache(managedAttribute);

Or retrieve the object again after saving to confirm if the change is actually applied:

managedAttribute = context.getObjectById(ManagedAttribute.class, managedAttribute.getId());
System.out.println(managedAttribute.getExtendedAttribute("yourAttributeName"));

Check logs for potential errors
Even if no error appears in the UI, something could be failing silently in the logs. Look at catalina.out or sailpoint.log to see if there are any warnings/errors when executing your updates.

4

there is no mapping for an application attribute. so this does not explain why even the proxy app is not updating. I will post the managed attributes mapping later today.

5

I am already doing this in my code. There are no errors. When I update the proxy app for an application , it gets updated briefly and gets reverted back.

6

It looks like something external is reverting your updates after they are applied. Here are some steps I can think of to help debug the issue:

1. Check for Background Processes or Syncing Mechanisms

  • Scheduled Tasks & Workflows: Go to Debug → Task Results and look for tasks running around the time of your update. A scheduled job may be overriding your changes.
  • Identity Refresh Task: If your update affects identities, check if an “Identity Refresh” task is reapplying old values.

2. Debug Object Persistence

Add debugging logs before and after your update to track changes over time:

Application app = context.getObjectByName(Application.class, "YourAppName");
System.out.println("Before update: " + app.getProxy());

app.setProxy("NewProxyApp");
context.saveObject(app);
context.commitTransaction();

System.out.println("After update: " + app.getProxy());

// Check again after 5 seconds (change it if you wanna test more time)
Thread.sleep(5000);
app = context.getObjectByName(Application.class, "YourAppName");
System.out.println("After 5s delay: " + app.getProxy());

If the proxy value reverts after 5 seconds, something external is modifying it.

3. Manually Update via Debug Page

Try manually updating the proxy via SailPoint Debug → Application and see if it still reverts.

  • If it does revert, something external is modifying it.
  • If it doesn’t revert, the issue might be in your update logic.

4. Enable Debug Logging

Update log4j.properties to track application updates (instructions to locate log4j.properties file):

log4j.logger.sailpoint.object.Application=DEBUG

For tracking database operations, add:

log4j.logger.sailpoint.persistence.hql=DEBUG    
log4j.logger.sailpoint.persistence.XmlType=INFO

Run your update and check the logs for unexpected modifications or rollbacks. Be aware that this may generate a large volume of logs, making it tedious to sift through—but if all else fails, this could be the best way to pinpoint the issue.

Let me know what you find! :rocket:

7

Hi @dmaan,
Just checking in to see if my response helped you.

If this solution resolved your issue, could you mark it as the accepted answer in the forum? This would help others facing similar challenges and also allow me to continue progressing on my journey as a SailPoint Ambassador.

Let me know if you need further assistance!