Error when enabling dropdowns in sub-concept

[ElevnLi]

Hey, this is Elevn, software engineer from University of Sydney and we are trying to fork and utilise Leaf to be the base of our clinical data management platform, Sanddi. And I'm having an issue regarding enabling dropdowns in sub-concept. Not sure if I'm using it correctly or there is a potential bug.

I created a SQL Set called fm_patient, in which I created multiple dropdowns, such as summary primary diagnosis, diagnosis certainty, etc. Then I created a concept called Patient and I'm able to enable dropdowns for this concept and it works fine. However, what I want to do is to create a sub-concept called Diagnosis and enable the dropdowns there, as I can't have all dropdowns from different perspectives all in Patient. Now I can see the dropdowns inherited from Patient in Diagnosis, but when I click a specific dropdown I want, it will run to an error like below.

Do you know what I might be doing wrong here? Let me know. Thanks a lot!

[ndobb]

Hi @ElevnLi, nice work! I think I follow but can you add a few pictures of the UI to make sure I'm understanding correctly?

Also, did you add dropdowns via the Admin UI or directly to the SQL DB?

[ElevnLi]

Hi @ndobb,

Thanks for being so responsive! I added dropdowns via the admin UI like below

And I'm able to enable them under Patient, which is the root concept utilising fm_patient_csv

However, if I try to enable dropdowns from sub-concept like below, it will raise that error after I click any of the dropdowns

[jnothman]

This error happens when the concept is not saved.

[ndobb]

Thanks @ElevnLi and @jnothman! This has been fixed in v3.10 https://github.com/uwrit/leaf/releases/tag/v3.10.0