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 :)

very helpful :)

@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

Congrats to the winners :)

This sounds like a classic example of leveraging embedded Python in IRIS to make use of the very large volume of python libraries that do just about anything :)  Here is an article that I found on a quick Google search on how to do this in Python:

https://www.geeksforgeeks.org/convert-pdf-to-image-using-python/

You could just leverage the Python capabilities of InterSystems IRIS to make use of how this problem has been solved in Python! 

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 :)  

John - FYI ... you can reach out to Support to help with issues like this.  Sounds to me like a bug that they we would want to jump on quickly.  Thank you for bringing it to our attention!!

Thank you for all of your hard work ... it's amazing to see how far this ecosystem has come in the past couple of years :)

thank you for sharing the learning John!

+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.  

Thanks Dan - it looks like that would be incredibly useful :)