Case table separation | Update assignment keys in DB
Class xxx-Work <-- Is Classgroup, mapped to Table T1
Class xxx-Work-AA <-- belongs to above Classgroup
Class xxx-Work-BB <-- belongs to above Classgroup
Current we have an application in production with hundreds of in-flight cases mapping to each of the classes above Work-AA and Work-BB. The management want to decouple the 2 case types AA and BB, since they belong to different stakeholders now (there are some project history, but what's done is done).
In order to decouple the case tables at DB level:
1) I've asked the DBA to create new table T2 based on same definition as T1 above.
2) Updated class Work-BB to "is a classgroup", and created class group rule for Work-BB
3) Created DB-Admin-Table instance to map Work-BB class to new table T2
What I did above worked well for newly created cases. But I'm running into issue for in-flight cases. It seems there is a mismatch between
Assignment pxRefObjectKey and Case pzInsKey. I anticipated this of couse, so I also asked the DBA to update the following fields to make sure they reflect xxx-Work-BB (new table) instead of xxx-Work (old table).
I'm not sure I follow what exactly you are doing, but the first thing that comes to mind is that you are making changes to objects in their exposed columns, but that the values in the blob are not getting updated. That means as soon as you open the object to work on it, the blob values will overwrite your changes in memory and when you save from within the system, your changes will be gone. You would probably be better off opening the objects from within the system and updating them as appropriate and updating the database via an Obj-Save.