Updated models are not captured in update set after publishing them to hardware catalog

[WA1]

Hello,

I published some hardware and consumable models to hardware catalog using the related link "Publish to Hardware Catalog" and in my update set I have only updates related to the new hardware catalogs created so I don't have the models updated with their catalog items (the field "Catalog item" is empty in the model record).

I thought about adding each model to the update set using the related link "Add to update set" or doing an XML export of the updated models and then importing them to the other instances but with this approach I may end up with duplicate models.. and updating the models manually in each instance is not the best practice.

How to deal with this issue please ? In normal cases should we force the models in the update sets ?

Thank you

[Mark Manders]

If you push them to update set or move them through XML, you will be overwriting the same records on the target instance (based on sys_id). So that should bring no duplicates in.

And models are data, so they aren't captured in update sets when you make changes to them.

[WA1]

@Mark Manders, the problem is that we have some models with different SYS ID in the instances, so by doing the XML import we will have duplicate models..

And yes I know that they are not automatically captured in update sets but I wanted to know the recommended way in other projects to make such actions..

Thank you

[Mark Manders · Accepted solution]

Best practice is to make adjustments on unique records when it's data. So cloning before making changes to models, so the sys_id's are the same. Or use a process for creating models. Either always create them on PROD and XML them back to non PROD instances, or create them on DEV, push them into an update set and move them further down to PROD.

Solution for now is to delete the models on DEV that have a different sys_id and xml the record from PROD to DEV and make the changes again, otherwise this issue won't go away and you will be running into the same, the next time changes are made on DEV.

Also: having different sys_id's can cause issues in logic. Because if you create a BR on DEV with model = xyz, the BR will be moved to PROD with 'model = sys_id_of_xyz', causing it not to work on PROD.

[WA1]

 @Mark Manders , thank you for your response it was helpful.

It will be difficult to identify the models in DEV that have a different SYS ID and delete them, we have more than 500 models to verify..

Is there some impacts if I delete them all from DEV and then import the ones we have in PROD ?