Being able to hide them is a request I get frequently, so if it’s something you are running into as well, maybe suggest it as a feature on the forum here, or put it as an issue on Github. I could imagine this being an additional setting available for each form.
In the meantime, one workaround for at least preventing people from creating new instances would be to use the query and newRowInitialElementKeyToValueMap to feed in a dummy variable – that would only happen if entering from the main form – and have an immediate constraint that the variable has to be one. This would therefore constrain creating new instances, at least, to going through the main form.
Thanks so much for the reply! Ahh, ok, I didn’t realize that, obviously. Thanks for clarifying. After submitting it, I realized that one answer to my question might be: “use Tables to design your form launching platform” and now maybe even more so! I just re-loaded all the demo forms and started exploring them from the Tables side. In the end that’s probably the best way to go anyway, I expect (is there any reason not to?). For others reading this chain, the second sentence here even suggests using Tables to launch your forms is appropriate: