No, this isn't possible today. Maximo removes all pending changes to ensure there aren't logic errors/remnants that weren't accounted for properly. It does this for most tables by simply removing the data in the CFG related tables (MAXATTRIBUTECFG, MAXOBJECTCFG, etc.) and reloading from the source object (MAXATTRIBUTE, MAXOBJECT, etc.). This is much more efficient than comparing column by column (search type, title, remarks, same as, length, scale, java class, etc.) and executing individual updates and deletes.
As for some potential logic errors you could have if there was a subset deleted, you could have SAMEAS settings where you discarded the object that you're supposed to have the SAMEAS settings for on another object being added. Something like auto number you can utilize the same AUTOKEY across objects (typically done when you're using views of the same object, but not a requirement) that you would have to know when to delete and when to keep.
The goal would be to utilize Migration Manager packages/DBC files for migrating the changes instead so you wouldn't have pending changes queued. I understand in practice that it's not that simple to do as they have their own limitations today (such as needing admin mode/restart for non-structural changes). But I think if we were to make improvements that's probably the area I'd see us improving.
------------------------------
Steven Shull
------------------------------
Original Message:
Sent: Sun November 28, 2021 09:38 PM
From: User1971
Subject: DB Config: Only discard pending changes for specific objects
MAM 7.6.1.2:
I've made changes to several objects in DB Config. I want to discard the changes to one of the objects before applying the changes.
Is there a way to discard the changes to specific objects -- instead of discarding the changes to all objects?
Thanks.
#Maximo
#AssetandFacilitiesManagement