[larasmith]

Is it possible to create dependent drop-down here in enterprise edition without modifying the core?

For example the first drop-down is Topic and the dependent drop-down is Subtopic.

Clicking the drop-down Topic automatically updates the drop-down list of the Subtopic.

For example the selected topic is Color and the subtopics are Red, Yellow, Orange,

if the user selects other topic such as Size then the subtopics to be displayed are

Small, Medium, Large the other subtopics not related to the topic Size

won't be displayed.

 

If it is possible, can you show example on how to do it?

Thank  you very much!

[larasmith]

Any ideas on this one?

It will be highly appreciated.

 

Thanks! 

[larasmith]

I'm still struggling in this one. 

 

I've tried using jquery but still no luck..

 

Any suggestions?

 

Thanks!

[larasmith]

This feature is useful and is extremely needed.

 

I just hope the development of this feature is prioritized.

 

My worst case scenario is switching back to the community edition which is able to do this feature.

[larasmith]

Still hoping for this one...

[larasmith]

And my hope never fails on  this one...

[larasmith]

Hopeful that this is in progress...

[web-johnny]

Hello @larasmith,

 

This functionality will be delayed as it is mainly difficult as it has lot of scenarios. However as it is always my pleasure to help people that uses Grocery CRUD (although without promises) I was thinking as Grocery CRUD Enterprise has a very strong core and the functionalities can be added as components, I was thinking to start creating some functionalities with name them "Kaizen" (the word Kaizen is "Continuous Improvement" in Japanese). I will give you an example. So let's say that I am creating the functionality depended dropdown list as Kaizen.

 

That will simply mean that the functionality is ready to implement it to your project however:
- It is not documented very well (e.g. the documentation is still under development)
- It is unstable for newer versions (e.g. in every update of the latest version you will need to check if the functionality is broken.)
- The development is not completed yet (we will have some changes at the future and they may be big ones)

 

The good news is that we will have some functionality that will work 100% (and of course considering that this can be used in production environments as well) but as the development will be as fast as possible we may have some instabilities as the architecture of the functionality wasn't well prepared.

I will give you some more specific examples. So far the difficulties that I am having with the depended dropdown are the following:
- As the requests on the server are many I can't test or design all the scenarios that we could have (e.g. it will take the most of my time to do that)
- Some JavaScript plugins are still in Release Candidate edition so they may change the way that they work at the next version

- Some small details may not work and it will need much more development to improve them (sometimes I am even writing the code from scratch or seriously contribute the development of the plugin)

As the functionality is in "Kaizen" mode however, I will clearly say it at the documentation that we will have some restrictions. For example:
- I will not spend too much time to answer difficult questions for a Kaizen version of a functionality (consider Kaizen as BETA version).

- The bug report for Kaizen functionalities will need to be clear and with as many details as possible or else they will not be considered at the bug fixing backlog.

 

A Kaizen version of a functionality will have down the list of known issues so the developers will consider them in case they want to use them.

So? What do you think @larasmith and everyone? Does Kaizen versions of some functionalities sounds good to you? If yes, then I will also announce it to the forums (or at a new blog that I will create?)

Remember that the dependent dropdown started as a work-around and now it is the most famous library in Grocery CRUD (with 100,000 views so far thanks to @victor :) )

 

Regards
Johnny

 

[larasmith]

Hello Sir @Johnny,

 

The Kaizen approach sounds good.

 

If this is implemented we can actually experience and test the feature being implemented and provide feedback.

 

We the users can actually contribute by using it because we can use it in different systems and further test where would a fix be needed.

 

Who knows that a Kaizen being featured can actually be a permanent feature of the Enterprise once its fully tested?

 

Let us keep improving and contributing for the betterment of our beloved GroceryCRUD.

 

Looking forward for this feature... Keep it up!  :)

[web-johnny]

Hello @larasmit,

 

Well I was thinking about having it in the title and as a warning at the very beginning of the documentation. Of course Kaizen will not be there forever but if all the known issues are solved then we will remove all the [Kaizen] notes. An example of some Kaizen features of Grocery CRUD community edition that confused lot of people were:

- Multiple grid [Some scenarios missed]

- dialog forms [Following a completely different approach from the normal edition. Risky for production environments]
- CSRF protection (it was a Kaizen as it wasn't working for IE browsers)

I am thinking if I didn't have the word "BETA" and have the word "Kaizen" with a link to the explanation (at the above post really) then people at least will understand whats the whole point of creating Kaizen features.

 

I am desperately trying to find time to do some development and apparently the 90% of my time is supporting users through emails :( And because developers desperately need some features to have Kaizen features is the best for both sides.

Let's see how it will go. So far I like the idea and the name  :D 

Regards

Johnny

[wildfandango]

it sounds really good, in terms of time I can only say that I understand you

go for it!

it sounds really good, in terms of time I can only say that I understand you

[larasmith]

After the date issues have been resolved, 

I hope that dependent drop down feature is next in line now...

 

This is going to be a big leap but indeed a very useful feature.

 

:)  ^_^

[larasmith]

Is there any progress happening for this feature? I hope there is...

So eager for it  :)  :)  :)

[web-johnny]

Hello @larasmith,

 

Unfortunately it is always a new feature coming first :(

For example currently I was having issues with latest PHP 7.2 version and MSSQL database.

 

Now my next feature request is multiple uploads. And till then I am also creating a documentation for Laravel.

 

I hope after multiple uploads that the depended relations will be next. I am seriously thinking to open a kickstarter just for depended dropdown list. It is the no1 request and... the most difficult one :( !

 

Thank you for you patient @larasmith you are really helping the community to grow

 

Regards

Johnny

[larasmith]

Sir Johnny,

 

It's okay. I will never lose hope on this one. :)  Sooner or later you'll figure it out. 

I just hope I can help you out too... Maybe you can post a dedicated thread for it?

Who knows maybe others can contribute too just like in the free edition.

 

Thanks and Regards,

Lara Smith

[web-johnny]

That's true! If anyone is familiar with React (https://reactjs.org/)  and Redux (https://redux.js.org/) and would like to help please send me a private message at: info@grocerycrud.com

 

The difficult part is the JavaScript part. The PHP is the easy one :)

Regards

Johnny

[larasmith]

Up for this issue this week...

 

Thanks!

[web-johnny]

So far this is in development but you can see a GIF video of the (real) progress that I've made so far. We have plenty more things to do (such as the dropdown list to be searchable) but I guess this will give a bit more patient for people to wait:

 

[attachment=1316:ezgif-4-37c80bb740.gif]

P.S. By the way I am spending the time that I have for holidays to release this functionality. I know this is tough for some people... but I like it to be honest :)

[larasmith]

Hello Sir Johnny!

 

I know you can do it! Keep it up. :) We'll be waiting for your next version release...

 

Off the topic... I was quite worried about the bug in using the where condition of setRelation.

There are two of us in the forum that observed such behavior:

1. /topic/4338-error-in-setrelation-when-two-relations-point-to-same-table-and-both-use-where-clause/

2. /topic/4356-error-in-clicking-view-button-in-setrelation-with-where-condition-and-setprimarykey/

 

I do hope these issues get resolved too.

 

Thanks again and more power!

[web-johnny]

I am very glad to inform you that the latest version of Grocery CRUD Enterprise (v 2.6.1) now includes the dependent dropdown list functionality  for more about it check: https://www.grocerycrud.com/enterprise/api-and-function-list/set-dependent-relation

https://www.