Missing related lists when using custom theme

Philip Hulshize
Tera Contributor

It seems when following the directions to create a custom theme, that ServiceNow loses the ability to display related lists.

I created a custom core default theme which I made at a higher order than Colors - which I also used as core. This theme works fine, and on requested items, sctasks, changes I see the related lists.

If I enable Dark Theme, and use the ootb dark theme, I also can see the related lists.

However, if I create a color theme as a variant using the method of using the Color Generator page, copying the json, and pasting into a variant theme - I get no related lists on many forms.

It seems there is something in the ootb themes that is not being added when you create your own themes.

1 ACCEPTED SOLUTION

Just adding the line " "isDark": "true"," to the UX Style JSON, it works.

View solution in original post

9 REPLIES 9

Mike_R
Kilo Patron
Kilo Patron

Very odd. You should definitely create a case with SN support. Sounds like a bug!

oh, it gets weirder, and I have seen it in my PDI as well. One of my instances, it works. All the other instances, not so much. Then I discovered they are actually there if you tab through the form. I then looked on the right side of the form, and the scroll down bar stopped short! Seen in Chrome and Edge.

I am assuming you do not have the problem?

I don't have the issue. However, I never created a whole new theme. I just created a new variant under the Polaris UX theme.

 

It could be that something is missing from your custom theme. You don't have the issue when you revert to the OOTB theme right?

So, these are variants just like you mentioned you created. ootb themes seem fine. I dug more, and it seems that for whatever reason, SNow is putting the form inside of it's own frame on these variants I created. So, the scroll bar stops short. If I go into the form, and hit tab, it jumps me to another frame at the bottom that has my related lists. Bizarre. HI said their is a problem ticket opened on it. It was open 2 months ago, so I do not have much confidence in a quick fix. I was/am hoping someone deeper entrenched in Next Experience had some insight.