Best practices when editing a GI that is linked to another GI?

Hi ​@SBaldwin , some best practices for me when I work on GI using another GI as data source are:

• Always exporting a copy of the original source GI and also the main GI. Especially the main GI, that way if something breaks, I can easily re-import and start refresh. 
• I also re-add the source GI to troubleshoot as well. This would give me a clean re-connection as I redo my joins. 
• After editing the source GI multiple times, sometimes I also like to reselect some of the fields in my conditions or results grid. From my understanding, this would let the GI reconnect to the fresh column list. 

Hope this helps!

My biggest worry is causing a cascade of unknown issues on screens I didn’t know were related.

Few recommendations:

• Use a different naming convention in the Inquiry title - i.e. prefix with a standard code to indicate that it’s essentially a subquery (still working on implementing this myself)
• Use the notes on the GI header and results lines to act as code comments
• Create a GI dependency checker by joining GIDesign and GITable on DesignID. GITable.Type=1 will be GI data sources while 0 will be DAC tables