Request for variable Showing empty in SC TASK List View

[Dileep Raju]

Hi Team
In my instance " Request for variable Showing empty in SC TASK List View. "

Can some explain me why it is happing and also What I need to do for Request For Variable in order to fill after submission of Ticket

[Anks26 · Accepted solution]

Hi Dileep, 

There could be few reasons why this could be happening, as there is an historical issue with ServiceNow request in my experience and tricky to explain.

There is a "requested_for" field on sc_request and a "requested_for" on RITM/Task, make sure you are displaying the right one on the list view. 

Previously, in your catalogue variables, you would use would ask "who is this request for" using reference "sys_user" table which would set "sc_request" requested for but not RITM requested for and different organisation handled it differently. i.e. using BR/workflow to keep them in sync but the ServiceNow introduced a "requested_for" variable type 
which fixed this issue. Not sure what variable you are using so try updating it to this type and it may fix the issue. 

 

 

Let me know if you have any other questions. As I said it's a little hard to explain. 🙂

Thanks

Anks

[priyasunku]

@Dileep Raju 

Are you talking about requested for field or customized requested for variable.

If my answer solved your issue, please mark my answer as ✅Correct & 👍Helpful

[Anks26 · Accepted solution]

Hi Dileep, 

There could be few reasons why this could be happening, as there is an historical issue with ServiceNow request in my experience and tricky to explain.

There is a "requested_for" field on sc_request and a "requested_for" on RITM/Task, make sure you are displaying the right one on the list view. 

Previously, in your catalogue variables, you would use would ask "who is this request for" using reference "sys_user" table which would set "sc_request" requested for but not RITM requested for and different organisation handled it differently. i.e. using BR/workflow to keep them in sync but the ServiceNow introduced a "requested_for" variable type 
which fixed this issue. Not sure what variable you are using so try updating it to this type and it may fix the issue. 

 

 

Let me know if you have any other questions. As I said it's a little hard to explain. 🙂

Thanks

Anks

[Dileep Raju]

Hi @priyasunku 
Thank you for quick reply
Could you please me for both requested for field or customized requested for variable ?

[priyasunku]

@Dileep Raju can you just provide screenshot of your field and also please tell me if it a custom or OOB field.

If my answer solved your issue, please mark my answer as ✅Correct & 👍Helpful