Secondary fields is missing in simple list widget

chrisrutherford
Tera Contributor

Hello all,

I am working on a client's instance and using the simple list widget.   However when I click on the edit properties I do not see the option for secondary fields which from what I understand is a very out of the box feature.

Has anyone else had this issue and know how to fix?   Very frustrating!

Thanks in advance,

Chris.

1 ACCEPTED SOLUTION

krushikesh
Kilo Guru

Hi there,



follow some following steps



1) Go to service portal configuration and open Designer


2) select your page ( for ex index)


3) Now click on pencil icon of your Simple list widget and you will see the form of simple list widge


4) Now click on Sandwich Icon and select Open in platform


5) Do form layout and move Secondary fields or Fields on the form



Or



you can add in Additional options, JSON format to display Secondary fields



{


"secondary_fields": {


"value": "number,sys_updated_on",


"displayValue": "number,sys_updated_on"


},


}



find_real_file.png



Have a great day


View solution in original post

3 REPLIES 3

Raju Koyagura
Tera Guru

Can you share the scree shot on which screen it is missing?


krushikesh
Kilo Guru

Hi there,



follow some following steps



1) Go to service portal configuration and open Designer


2) select your page ( for ex index)


3) Now click on pencil icon of your Simple list widget and you will see the form of simple list widge


4) Now click on Sandwich Icon and select Open in platform


5) Do form layout and move Secondary fields or Fields on the form



Or



you can add in Additional options, JSON format to display Secondary fields



{


"secondary_fields": {


"value": "number,sys_updated_on",


"displayValue": "number,sys_updated_on"


},


}



find_real_file.png



Have a great day


Hello Krushikesh, thanks for your response.



I was able to add secondary fields via the JSON option.   After inspecting using the form designer I discovered the secondary fields were not an option.   Makes me wonder if the client had previously eliminated them somehow or if there is some other issue with the instance.



Cheers.