Can someone please explain the role of the DXA Resolver and the Generate Data Presentation CT and how it affects building up the Page model?
I understand that you must link the desired Schema to said CT for it to be processed by the Resolver, I just don't understand why this is needed.
Correct me if I'm wrong, but DXA with the Model Service (2.0 and above) can handle both embedded and dynamic CPs perfectly fine, so why complicate things by introducing another concept? Are these data presentations treated differently by the Model Service in comparison to "regular" DCPs?
I have gone through the official documentation and various other online sources half a dozen times, but I seem to be having a brain freeze and am unable to grasp the concept at the moment, nor is everything properly explained/documented.
Some of the explanations say:
The DXA Resolver ensures that the linked Dynamic Component Presentations are automatically republished
If I have a Page which has DCP added to it directly, the DCP gets published by default so why the need for the Resolver? Or is this not a valid use case?
OR
When publishing a page, the resolver takes care of publishing a Dynamic Component Presentation (DCP) for every component on the page which is using a Schema linked to the Component Template titled “Generate Data Presentation”
So the Resolver adds a DCP to be published for all of those Components, the CT being be the Generate Data Presentation, right? But why would I need this? How does this affect the Model Service and its building the model?
And finally,
- Does it make sense to to link any Schemas which only have embedded CTs linked so far, or should this be used only for Schemas which already have a dynamic Template associated?
- Should all Schemas which already have a dynamic Templates linked be linked to the Generate Data Presentation? Or are they all just candidates, and some additional condition/use case must exist for this to make sense?
