-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request — Display relational field in the list view #7
Comments
Linked to: #8 |
I am willing to try and co-develop this feature. If it’s okay, here are a couple of thoughts and questions:
|
being able to introduce relations into the filter like other displayable columns will be awesome |
I think a link there to the corresponding 'students' of a school, aka students filtered by school to view and edit would be awesome.
Do you mean something like str methods in django models?
|
I like the idea
I'm not sure. I haven't used django. What I ended up doing is storing methods in the global |
Here's my work around on this limitation I got the same problem displaying category type on list view of my article collection. I created a read-only field on article collection then when the user selects a category, I will then save the name of category to the read-only field. Finally, you can display that read-only field on the list view. Hope it helps. This solution is inspired by this link *Sorry for my bad english. |
@alexey-yunoshev do you happen to have the code you implemented publicly available? I could definitely use the filtering part |
@alexey-yunoshev I would love to see the code for that as well, if possible! |
Hello everyone We have been working on this feature with the team and I wanted to let you know what we plan. For those I haven’t met yet, I am Samuel, product manager at Strapi. I joined the team a couple of months ago. Before giving you an overview of the feature, I just would like to let you know that for the next features we all want to better collaborate with contributors and members of the community. Even if we haven’t discussed this feature with you here in this RFC, your feedback and input have been really valuable and helped us work on it. We’ll also communicate more broadly on features development to explain our choices, our constraints, and our vision. The goal is always the same, making Strapi always better and share as much info as possible with the community to help you implement it the best way possible, work with it, and contribute to it. It is a bit long and heavy, feel free if you have any question or want me to clarify a point 🙂 |
Here we go! We have started working on the display of relational fields after the Draft&Published feature’s development began. With Maeva, product designer, we still needed to understand what admin panel users are trying to achieve through list views in general (not only through the display of RF), why do they need to have more info there, which info, which actions, etc. We conducted several user interviews and could test some early-solutions prototypes. I’ll share more info later in a blog post about what we learned during this research but here is a quick overview of the feature so you know what to expect, and we can discuss it. Here is what we decided to implement in this first version of the feature: As you said here in this RFC, we can’t manage x-to-many relations values the same way we do for x-to-one values. The tables wouldn’t scale well if you have 30 values in a cell. So we are going to manage them differently. It will be possible to display one field by relation. The users will be able to select the relations they want to display in the list views but the corresponding relational field will be automatically synced with the one set as « Entry title » in the Edit view settings. Even though this choice can limit customization in the List view, our research showed that List views and Edit views go together and need to have coherence. That is the choice we made: coherence of the information on both views > customization of the List view. As we sync with the field selection with the Edit view, the same restrictions automatically apply: it won’t be possible for the moment to display components, dynamic zones, and polymorph fields Displaying relational fields means adding more columns to the tables, with Draft&Published and later Internationalization (18n), more and more columns will be added too, which means a higher probability of having narrow columns and cropped cells. So until we adapt our tables to scale, we decided to add tooltips to cells where the content is cropped. This will allow the users to view the content of a cell even when cropped. Now about sorting, searching, and filtering. Searching on relations would be too harmful to performance, so we decided to not make it available for the moment. One solution we have in mind for later would be to create an integration with dedicated search tools (Algolia, Elastic, etc.) to make the search in the Admin works well at this level, though we won’t be working on it soon. About filtering, we use deep filtering on relations, though we decided to limit it to the “Entry title” field of each relation. To make deep filtering available for all fields of a relational requires us to improve the filter UI/UX to accept one more input (relation and field and not only field). We’ll keep improving this feature regularly, and we identified several areas and features we’ll have to improve in the near future regarding relations and views 💪 Let us know what you think! |
@alterx @mryechkin The code I wrote is a part of a private repo, and it would take a lot of time to extract it, which I unfortunately don't have right now. But from the messages above, the official solution is coming, so I wouldn't bother building anything custom that is so deeply integrated, because in the future it might make it more difficult to update to a new version of Strapi. |
Hi @sam-pires do you already have any feelings on when you might release this? |
Hello @jankallewulf, |
@sam-pires thanks for the details and keeping us up to date! Looking forward to having this feature available :) |
looking forward to this. thank you @sam-pires and team |
Hello everyone, Quick update as promised, we are still aligned with the previous message 🙂 Have a good morning/day/evening! |
Do you envision bringing this type of relational field display for component interfaces as well? For example this component has a relational field and it would nice to be able to list the Property title in this view as it is now we just use the ID in the UI which is not very helpful without expanding the element: |
humm 🤔 |
So after we discussed that, I can confirm that we don't improve that behavior in the upcoming feature, but we'll definitely have a look at it! |
Hi @sam-pires, hope you are doing well! As the feature is still in development and not yet in testing, would it be a fair assumption that the feature will come more like a Christmas present and a release within the first half of December is unlikely? |
👀 🎁 I'll let Sam answer 😉 |
Hello @jankallewulf, I'm doing well, thanks 👍 , hope you too! Indeed expect the stable version of the next release around Dec 15th. The "exact" schedule we have in mind is:
|
Hello Hello 🔥 Good news everyone we released the beta for Strapi 3.4 which includes Relational Fields! You'll find more info on the forum https://forum.strapi.io/t/new-beta-release-strapi-v3-4-0 Please test it in your conditions with your usual workflow and data if possible ( The doc and detailed changelog will be available later, so it's gonna be a bit of a discovery haha. I listed some features in the post on the Forum though, that should help. Give us as much feedback as possible, if it's good, bad, not-intuitive, buggy, the best experience of a software you ever had... share it on the forum or here or through Github issues so we can take them into account and improve it for the stable 💪 Thanks everyone, I hope you'll like it! |
Hi @sam-pires, just downloaded and tested it. Works perfectly. For the next release I would prefer to have also a visual representation (like suggested here: strapi/strapi#6329) to make it easier to immediately see the connection between the content items. Nevertheless, great work and I'm extremely looking forward to updating to the stable release hopefully soon |
Hi all Strapi v3.4.0 was released today: @alexandrebodin / @sam-pires I'll let you guys close out the issue. |
Closing this RFC as the first version was implemented. You can now go to the forum to give us your feedback 🎉 https://forum.strapi.io/t/new-release-strapi-v3-4-0-with-relational-fields-in-list-view/1689 |
Thanks everyone for your involvement in this feature! 👍 It is great to have such an active community and to be able to interact with you directly! I am looking forward the next RFC we'll work into a feature. |
This issue has been opened because we (as the core team) are looking for contributors to help us co-develop the feature.
Link to the roadmap
Motivations
The list view of the Content Manager doesn't display the relational fields. It only displays simple fields (text, number, boolean, etc) and media.
For instance, when you look for all the blog posts written by a specific user you can't. You have to go to the details page to know the author of the blog post.
Tasks
Risks
In other words, the list view must handle one-way, one-to-one, one-to-many, many-to-one, and many-to-many relationships.
The text was updated successfully, but these errors were encountered: