The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Regarding query used idalko multi level cascade field

Rohitkumar Gupta
February 17, 2021

Hello All,

 

We are using Idalko multi level cascade field and created 7   levels in the field.

The level are dependent on each other.

 

The issue im facing is the query is getting long level by level.

Its take time to load values on the screen because of long queries.

 

Can anyone help me to reduce the queries so it will take less time to load on the screen.Capture17-2-21.PNG

 

Regards,

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
February 17, 2021

You've quite simply got too many levels in there.  Why are you doing this?  Reading the names of the levels across the top of the definition, tells me you're building a totally unwieldy and pretty much useless flat field from a load of things that should not be done as drop-down.

What would the purpose of this field be?  What benefits would the end user get from being able to select at this level?  Do you really identify individual items of data by their version, description, task etc?