Accessing cascading fields via automation
Asked by Arturs Kalnins:

I have a cascading field called "business impact" that is required upon creation.   

I'm trying to set up an automation for a project that once A specific issue type is created an automation creates a new ticket for a team with some of the fields copied and some of the fields pre-filled. However i'm struggling in accessign the business impact field via JSON.   

![Screenshot 2024-07-22 102318.png](/t5/image/serverpage/image-id/336939i343BCB876EE940AE/image-size/large?v=v2&px=999 "Screenshot 2024-07-22 102318.png")


Answers:
author: Zuri Suwru
body: Hey Arturs,

Using the same JSON logic you have on your screenshot, I've successfully modified a cascading select list.

Could you please head into the "Audit log" tab and see what the error message you receive is once running your automation?

Bests,  
Zuri S.

comments: author: Arturs Kalnins
body: is your cascading field mandatory? I'm trying to create a new issue with a mandatory field.   

As there is no option within data center automation to copy from the trigger issue (as i am unable to access the field) It won't create the issue for whatever reason


author: Zuri Suwru
body: Yes, the field is mandatory. Please double check whether the values you entered in both your "value" fields are correct. The only way I receive the same error as you do is if I deliberately put a typo in my test case's value(s).

Working outcome where both values exist in my system:

![Correct.png](https://community.atlassian.com/t5/image/serverpage/image-id/336956iEE4CDF84F08CB67B/image-size/large?v=v2&px=999 "Correct.png")

![Correct2.png](https://community.atlassian.com/t5/image/serverpage/image-id/336955i0FF885F1E1B494EE/image-size/large?v=v2&px=999 "Correct2.png")

Error message when non-existent values are pushed, aka the JSON code, albeit syntactically correct, cannot run:

![Incorrect.png](https://community.atlassian.com/t5/image/serverpage/image-id/336957iE3320565A37E192D/image-size/large?v=v2&px=999 "Incorrect.png")

![Incorrect2.png](https://community.atlassian.com/t5/image/serverpage/image-id/336958i0227DD3B09CF845D/image-size/large?v=v2&px=999 "Incorrect2.png")

Could you double check the parent and children names in the JSON code?


author: Arturs Kalnins
body: [@Zuri Suwru](/t5/user/viewprofilepage/user-id/5158381) I appreciate the quick answer.

<br />

I double checked the values and the issue still persists.

are you on Datacenter environment? ![Screenshot 2024-07-22 124232.png](https://community.atlassian.com/t5/image/serverpage/image-id/336969i874ED1DE5F782FBB/image-size/large?v=v2&px=999 "Screenshot 2024-07-22 124232.png")


author: Zuri Suwru
body: Yes, I'm on Data Center. On the picture you've attached, is that by any chance a space at the end of the value or it's simply an artifact on the image?  
![space.png](https://community.atlassian.com/t5/image/serverpage/image-id/336983i47E16112D308B212/image-size/large?v=v2&px=999 "space.png")


author: Arturs Kalnins
body: Hi [@Zuri Suwru](/t5/user/viewprofilepage/user-id/5158381)   
It worked :) Thank you for your support!


author: Arturs Kalnins
body: When i'm running this automation, Audit log is showing following issue:  
![Screenshot 2024-07-22 110958.png](https://community.atlassian.com/t5/image/serverpage/image-id/336945i59D715A7C11C3813/image-size/large?v=v2&px=999 "Screenshot 2024-07-22 110958.png")


Tags: automation

data-center

jira-data-center

json