Paul, are you using the 3.0 or 5.0 manifest version format? In 5 there is the EventQueue but I am not sure this is going to do what you need to do. 

Another option, especially since Profile properties are portal specific, is to check for it's existence in your module on page load/init. Then, if it doesn't exist create it on the fly and then add the returned profile property definition ID (or something, maybe true/false) to your module settings. This will allow you to avoid having to check on subsequent requests again since you can just check the module settings to see if it already exists for that portal (and module settings are already stored in cache regardless of you adding this to it or not). Then, to clear it out on uninstall you can just add some logic to your uninstall.SqlDataProvider to delete it then (but be careful here, you don't want to delete valid properties). 

---

Chris Paterra

Get direct answers to your questions in the Community Exchange.

The ones that have a null portalid are the original properties that are strongly typed in the code (country, postalcode, firstname, etc.). You should notice that each portal also has their own copy of these. So to answer your question, yes they are portal specific. 

---

Chris Paterra

Get direct answers to your questions in the Community Exchange.