I’m using a shared block similar to the example shown in the dato docs.
The shared block is meant to be for all pages and it includes a title, seo, and slug fields so that I don’t have to redo these and keep them up to date with changes across different page types.
The issue is for models I can’t set the title in the shared global page block to be the preview title for the record and instead it requires a field that is on the model itself.
Is there any work around or do I have to include a field I want to use as the preview title shown in the admin on the model itself and not use a shared block.
In this example shown here with Bloggable shared type the title can’t be selected as the preview field for the model it is on and this is the problem I’d like to work around.
Screenshot of what the schema settings allow for preview only showing fields on the model itself and not in the shared block
Sorry, all I have so far is an interim update: I can confirm that this behavior is technically considered “by design”, which just means it’s not considered a “bug” that we can immediately fix Sorry about that.
That said, we do agree that it would be a nice feature to consider adding. It’s one of the things that will be looked at in more depth in the next development cycle. That means actual implementation (if it happens) won’t be for a few weeks or months at the earliest, unfortunately.
I’m going to convert this into a feature request, instead, and I’ll update this thread as more decisions are made in the next few weeks, either way (i.e., whether it gets chosen for development or not), and provide ETA as I can. Still, to be clear, I have to emphasize that so far this is just a “maybe” that may or may not happen soon.
I’ll update more as soon as I can. Sorry about that!
We have the same issue where we have a shared Hero component used across pages.
At present we use a Computed Field (Using Computed Fields plugin) to bring the hero[locale].heading from the component field back so it can be used as the “Preview Title” and also the “SEO fallback title”.
Unfortunately, we can’t use “Computed Fields” for images so we don’t have a solution for the page image which is also currently in the Hero component but can’t be referenced for the “Preview Image” or “Fallback social card image” so are having to set the social card image manually. Would be great if a solution could be looked at for that also!
Thanks Daniel for the solution, I started going down this path as well with computed fields but wanted to avoid additional plugins if I could.
The issue with computed fields is now I need yet another field at the model level which in my case the whole point was to have the “Internal Title” be something that was required for all models be shared and then set as the presentation title without requiring another field in the models themselves
A built in solution in datocms that supports all the fields types would definitely be great!
Thanks for the update Roger! Hope its something that gets picked up and also one other suggestion is in the docs I referenced for Bloggable the feature looks really nice to share fields but it doesn’t point out this limitation which I think could be important for someone following the docs and setting their schema up in a similar way and expecting it to function that way.
The preview fields in the Presentation tab only affect what your editors see. This is what we’re evaluating in the feature request (i.e., allow them to look into blocks to get their titles/images).
But the SEO fields (in the SEO tab) are totally separate, and normally you can control that just by using a different GraphQL query combined with some simple frontend logic (i.e., fetching the image details inside the block along with your record, and have your frontend use that to generate SEO tags). Could that work for this part?
For the presentation preview fields, I’ll still provide an update as soon as I get one. In the meantime, as a workaround, I think it would be possible to write a simple custom plugin using buildItemPresentationInfo() to customize the editor-facing display using whatever blocks/fields you like: Customize record presentation | Documentation — DatoCMS
Let me know if that is at all interesting… hopefully the documentation is clear enough, but if you would like to try that workaround and find yourself needing help, let me know!
Sorry about that.