No ... all kit distribution to supported customers is through the Distribution section of the WRC.  

This was more to figure out the proper way to do this in order for tracking for the badge, etc on the G.M. platform.  It makes sense that it needs to originate in a challenge (and than you to Olga for pointing that out).

I don't think that just having a form on the D.C. to invite a friend necessarily makes sense, as anyone can just shoot a friend an email with the link.  If others would like to see this as a new feature I won't object though.

Thank you @Olga Zavrazhnova!  I knew I had seen it somewhere at some point.  I just had a conversation with a new colleague yesterday about the value of the D.C. and Global Masters, so I will send her an invite :)

I thought that Windows containers still have issues?  Or is Windows on Docker at full parity now with Linux on Docker?

Thanks Bob - that's a great reference to be aware of (I hadn't seen it in the docs before)

@Julian Matthews  - it is never too late :)  Since you know the exact version that you were upgrading from / to, I think you're in the best position to still report this as a bug to the WRC.  They can then test to see if it's still an issue on the latest versions and they can log an internal bug if that is that case.  I would encourage you to still take a little time and ensure it is officially logged.

did you report this as a bug to Support?  it seems to me that this value should always persist since an upgrade shouldn't change the function of the environment 

great!  thank you for letting us know the solution :)

@John Murray  - the fix did go out last week and was just re-tested this morning, so you must be hitting something different.  Please click on "Submit Feedback" in the Cloud Portal and include the specific details of what you are seeing and Support will take a look at why your attempts are still failing and will work with you directly.

@John Murray  - I will reach out internally and will let you know

always a pleasure John :)

@John Murray  - I was just informed that the cloud team is aware of the issue and they plan to push a fix this AM.  No need to contact Support on this one :)  

+1 - this is a very useful way to instrument your code.

+1 to the Source Control recommendation

Ahh ... if they need to be used elsewhere then that is a different story.  

I forget off the top of my head exactly how this would work, but you could potentially subclass your Org class and just add the parent cardinality relationship.  I *think* that should force the extent of the subclass to be embedded in the parent class ( @Dan Pasco?), which should automate the cascading delete for you without impacting the Orgs stored independently.