Once you've deployed the custom property, it needs to be supported until you've removed it from all content which uses it.
The primary difference between a custom property and a customparamset is structure. Customparamsets are a generic custom property for end users to do quick and dirty stuff. They have very little support for PPGLayouts and cannot be identified from script code as all CustomParamSets have the same 'type' (customparamset). The only way you can identify them is by name or by comparing parameters. That is why the self installing CustomProperty was invented. I've never heard of wanting to migrate from CustomProperty to CustomParamSet, so this is a bit odd. Matt From: softimage-boun...@listproc.autodesk.com [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Alan Fregtman Sent: Thursday, June 13, 2013 11:00 AM To: XSI Mailing List Subject: Anyone got a tip to convert a customproperty to a regular customparamset? Hey guys, I have a customproperty defined in a plugin and it is used in a few assets, but I no longer care for the plugin and just want it to be a regular customparamset, however, Softimage complains that the plugin doesn't exist. Is there a trick to converting a customproperty to a paramset without having to recreate parameters one by one? Any help appreciated. Cheers, -- Alan
