Conditional fields | Content Editing XP

Conditional fields

planned

Pierre Burgy

Display a field only if some conditions are met.

March 21, 2022

Aurélien Georget

Pinned

Hey everyone 👋
It's Aurélien from Strapi, we added this in our roadmap for next year. So far, it's scheduled that we would start working on it in in Q2 and expect a delivery in Q3 (August). Please continue to post your use cases, the more you share, the better it is for us to adjust the solution to your problems.
----
May 2024 update
Due to the additional work required on Strapi 5, we delayed this feature. We delayed this feature due to the additional work required on Strapi 5e. We will keep you posted once a squad will start to work on it.
✌️

Harvey Gomez

Following this as it is a feature we require also.

I can build a custom plugin in the meantime but would be great when this is supported out of the box.

Brianfbento

Aurélien Georget With v5 launching soon, any update on this? Really looking forward to this feature

Aurélien Georget

Brianfbento I'm going to disappoint you. We didn't start to work on the feature yet. It's still in our backlog though. I have no ETA to share, it's on hold, the Preview feature was prioritized instead.

Davomyan

Aurélien Georget Hi Aurelien, what is the ETA on this now? Can we expect it still in 2024?

Aurélien Georget

Davomyan I still don't know, we are focused on fixing Strapi 5 bugs and the Previews as we speak. I don't think we should expect anything coming from the core team this year.

Franz Josef Kaiser

Thanks for the awesome work and for providing a public, managed roadmap with updates!

Questions:

Will this feature be "ee" or generally available?
Will conditional fields be able to toggle components as well or just single fields?

Thank you!

Aurélien Georget

Franz Josef Kaiser So far, we never discussed it about making it a paid feature. Nothing is written in stone, there is an high chance that the Conditional Field will be part of the Community Edition (aka free for everyone).

The second question is a good one, I'd say that the end goal is to also be able to toggle components (group of fields), for the first iteration and release, we may not support this.

Dimitris Kottas

Hello,

I just wanted to ask if the schedule is still for August 2024. We are starting work on a big project where this would be an important feature.

Aurélien Georget

Dimitris Kottas Hello Dimitris, I'll update the schedule as we got some delay on v5 and we want to focus all our efforts on it. Please do not expect this feature being ready for August 2024. I'd suggest to explore the custom field to build your project instead.

Bahadır Yaren

Here are a few more thoughts on the mandatory fields, perhaps from a different perspective. The fields where you cannot create an entry if the field is empty
In the image component of Next.js, the width and height props are required, unless fill prop is set to true.
See the documentation on https://nextjs.org/docs/app/api-reference/components/image#fill.
Some may need to define aria-labels, but either one of aria-label or aria-labelledby.
I can imagine a grouping of required fields where one set of fields is mandatory.

Kuba Raźny

any news?

Jonathan Hsu

Excited for this feature. It has the opportunity to tremendously increase the robustness of the data that can be stored via Strapi while maintaining a high level of data integrity (through the conditional fields). I have a lot of experience in building complex data collection forms that use formulas, visibility conditions, and field validation so I'm happy the Strapi team in any way I can.

Derrick Mehaffy

marked this post as

planned

Alex Bennett

Derrick Mehaffy: this update notification got me excited.

Aurélien Georget

Hey everyone 👋
It's Aurélien from Strapi, we added this in our roadmap for next year. So far, it's scheduled that we would start working on it in in Q2 and expect a delivery in Q3 (August). Please continue to post your use cases, the more you share, the better it is for us to adjust the solution to your problems.
----
May 2024 update
Due to the additional work required on Strapi 5, we delayed this feature. We delayed this feature due to the additional work required on Strapi 5e. We will keep you posted once a squad will start to work on it.
✌️

Laurens Kling

Aurélien Georget: This is great to hear <3 The use case is pretty simple. Lets say you have a Background component. You have a select box for what kind of background it is, a primary color, etc, or a custom color. Now when the user select custom color you want to show an input to add that custom color string. Right now, that input will always be there, but it will never make sense to be there outside of the custom color context. This our UI is filled with edge-case inputs which make editing difficult and confusing.

Brad Douglas

Aurélien Georget: This is great to hear! I've been waiting for this functionality to be added for a while. My use case is to look at how ACF for WordPress uses Conditional Logic when building out field groups. It exactly what I would expect. One quick use case: I give choices to the content editor (Choice A, B,C), they choose, then the proper fields show up for them to add the content.

Brianfbento

Aurélien Georget: Any chance we could include tabs as part of this? :D

Aurélien Georget

Brianfbento: The chances are low, a tab system will be introduced for Draft & Published, we won't offer any extension possibilities for the first iteration, however, the component is here and it will create future opportunities :)

Rihards Simanovics

Aurélien Georget Is this feature will be exclusive to V5 or will it be added to the V4 as well?

Aurélien Georget

Rihards Simanovics It will be only available on v5 as we plan to release "Strapi 5 Preview" in June and "Strapi 5 Stable" in September

Rihards Simanovics

Aurélien Georget, I see, this is unfortunate. Also, one other thing, heard Strapi team is revamping the pricing model, I hope this feature will be kept free as I foresee a lot of developers needing it.

Aurélien Georget

Rihards Simanovics There is no plan to make this a paid feature. We try to only monetize the features that bring value to the very advanced use cases or generate a lot of value for the users without compromising the customization part.

Rihards Simanovics

Aurélien Georget, I see, many thanks for clarification 😊

Adwin Ang

This would make a lot of solutions so much more elegant

→