# Fetch rest of the slices in Graph Query

**URL:** <https://community.prismic.io/t/fetch-rest-of-the-slices-in-graph-query/10578>\
**Category:** Developing with Prismic\
**Tags:** product-feature-idea, rest-api\
**Created:** [July 8, 2022, 10:14pm UTC](https://community.prismic.io/t/fetch-rest-of-the-slices-in-graph-query/10578 "2022-07-08T22:14:46Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![louie](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/louie/32/4766_2.png) [@louie](https://community.prismic.io/u/louie)\
**Post date:** [July 8, 2022, 10:14pm UTC](https://community.prismic.io/t/fetch-rest-of-the-slices-in-graph-query/10578/1 "2022-07-08T22:14:47Z")

</div>

Hey Prismic team,

I've recently run into an issue fetching nested data within a content relationship field.  
It was due to not being able to fetch all the RichText field in a fetch link query, so I had to use a Graph Query instead.

The problem I am facing is that there is no way (at least I don't think there is), to fetch the rest of the slices with something like `...slices`.

Here you can see I have fetched the required nested content in a slice, but now it will only return this one slice.

 ![Screenshot 2022-07-08 at 23.11.08](https://europe1.discourse-cdn.com/flex013/uploads/prismic/original/2X/5/52fc0f7116254bda64bbcbac552d7d8c9fe66344.png)

For now, I have done a temporary solution and added in all the other slices manually.

 ![Screenshot 2022-07-08 at 23.11.17](https://europe1.discourse-cdn.com/flex013/uploads/prismic/original/2X/2/26df41473c2a3be4676d8e22dca6c19bf5916054.png)

It would be nice if we could add something like `...slices` like we do for the homepage custom type (`...homepageFields`).

I hope this makes sense! :)

Thanks

---

<div class="post-metadata">

**Author:** ![Priyanka](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/priyanka/32/3223_2.png) [@Priyanka](https://community.prismic.io/u/Priyanka)\
**Post date:** [July 12, 2022, 9:29pm UTC](https://community.prismic.io/t/fetch-rest-of-the-slices-in-graph-query/10578/3 "2022-07-12T21:29:25Z")

</div>

Hello @louie

Welcome to the Prismic community, and thanks for your feedback.

For the moment, you need to specify each slice name to retrieve them and retrieve different fields related to another document; you need to specify the content relationship name too. I agree with your feedback and added it as a product feature idea, but It's not on our roadmap for the moment.

Thanks,  
Priyanka

---

<div class="post-metadata">

**Author:** ![juan.manuel](https://avatars.discourse-cdn.com/v4/letter/j/45deac/32.png) [@juan.manuel](https://community.prismic.io/u/juan.manuel)\
**Post date:** [February 28, 2023, 11:00am UTC](https://community.prismic.io/t/fetch-rest-of-the-slices-in-graph-query/10578/5 "2023-02-28T11:00:25Z")

</div>

We have the same issue.  
Our project has many slices, having to add them all here is very verbose.

---

<div class="post-metadata">

**Author:** ![Priyanka](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/priyanka/32/3223_2.png) [@Priyanka](https://community.prismic.io/u/Priyanka)\
**Post date:** [March 3, 2023, 11:15am UTC](https://community.prismic.io/t/fetch-rest-of-the-slices-in-graph-query/10578/7 "2023-03-03T11:15:42Z")

</div>

Thanks @juan.manuel For raising the point for this feature request.

---

<div class="post-metadata">

**Author:** ![s.vanderheide](https://avatars.discourse-cdn.com/v4/letter/s/6a8cbe/32.png) [@s.vanderheide](https://community.prismic.io/u/s.vanderheide)\
**Post date:** [March 29, 2023, 3:17pm UTC](https://community.prismic.io/t/fetch-rest-of-the-slices-in-graph-query/10578/9 "2023-03-29T15:17:18Z")

</div>

While working on our project we're having the same issue. Is this feature on the roadmap, if so, when can we expect it to be released?  
It would be nice that the graphQuery is not needed at all and that the data of the fields with a content relationship is retrieved automatically.

---

<div class="post-metadata">

**Author:** ![Pau](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/pau/32/5422_2.png) [@Pau](https://community.prismic.io/u/Pau)\
**Post date:** [March 29, 2023, 5:18pm UTC](https://community.prismic.io/t/fetch-rest-of-the-slices-in-graph-query/10578/10 "2023-03-29T17:18:11Z")

</div>

We understand your concerns and want to be transparent with our communications. Please note that the current functionality won't be changed, as each slice must be called individually, and there is no option to call them all with a single node name. Although GraphQuery syntax is similar to GraphQL, it is a separate tool.

---

<div class="post-metadata">

**Author:** ![jonathan.loss](https://avatars.discourse-cdn.com/v4/letter/j/f0a364/32.png) [@jonathan.loss](https://community.prismic.io/u/jonathan.loss)\
**Post date:** [November 29, 2024, 3:21pm UTC](https://community.prismic.io/t/fetch-rest-of-the-slices-in-graph-query/10578/13 "2024-11-29T15:21:24Z")

</div>

I agree, being able to write something like `...slices` is a badly needed feature. And weirdly on one of my custom types it seems to work without doing anything, and on others if I specify a slice for which I want specific content, then all other slices are just bypassed...  
I don't understand how this can not be a basic feature of graphQuery. Especially given there's a limit to the number of characters in a graphQuery, if there are enough slices in a custom type it's not just verbose to specify each slice name, it might be impossible !!!
