We have had some CI Classes in inappropriate Families and we want to move them to different Families. In some cases the old and new Families have different Extension tables.
We are looking at trying something like:
- For existing CI's, create a row in the appropriate Extension table for the new Family with attributes set from the existing Extension row (where available). We were thinking of doing this at the SQL Server level.
- Update the Class definitions to the new Families
- Restart CASDM
Would people expect his to work?
Later on we might clean-up the old rows from the Extension tables.
Note that we are using r12.6.