You can add a id on submission of the dialog with a PostProcessor:
https://sling.apache.org/documentation/bundles/manipulating-content-the-slingpostservlet-servlets-post.html#slingpostprocessor
But a model is tied to a specific resourcetype?! The 'model' selector only forwards the request to the sling-model if there is a model registered at the resourcetype of the pages content-resource.
This is not using the sling-model-exporter framework at all. And worse: It responds to all cq:Pages i.e. default-get-servlet and not only to specific page-resourcetypes!
We are currently working with a headless approach and I'm trying to estimate pros & cons of having more selectors in addition to 'model' at the cq:Page component. After digging through the request log and basically discovering what @Jörg_Hoh also mentioned here: https://cqdump.wordpress.com/2019/01...
I had some trouble while using Sling Resource Merger & includes too (in 6.1 though). From my experience I can say: don't use both together! Either use the Resource Merging mechanism or includes separately.
Great hint!!!I wonder that I can't find any reference to this within the official docs. Did I miss this feature at the 6.2 release-notes or somewhere else?