UI builder bug after Utah release on a PDI - [object object] instead of labels

T_Fesenko
Tera Contributor

Hi Community, 

While working with the UI builder on my PDI the interface of the UI  builder doesn't display labels correctly. This has happened multiple times throughout the last several weeks after the Utah upgrade.  

T_Fesenko_0-1680254196298.png

Apart from that, after I set certain css properties (setting with to 100%) and saving the values are lost. 
Possibly - a bug after the Utah release, but could it be a PDI issue? Anyone else experiencing this issue? 

@Brad Tilton is this a known issue?

Kind regards,

Tymofii Fesenko 


1 ACCEPTED SOLUTION

Brad Tilton
ServiceNow Employee
ServiceNow Employee

Hi Tymofii, I did a quick search and haven't seen anywhere else someone has reported this. You might try clearing the cache on your PDI or zbooting it.

View solution in original post

6 REPLIES 6

Brad Tilton
ServiceNow Employee
ServiceNow Employee

Hi Tymofii, I did a quick search and haven't seen anywhere else someone has reported this. You might try clearing the cache on your PDI or zbooting it.

Thank you, it indeed seems to have been resolved by clearing the cache. 

After further investigation it turned out that clearing the cache helps with the display issue but another one remains: 

My colleague and are working on the same UI page (btw, we use source control). For some components only my colleague is able to save changes. When I make them and click "save" - they don't get saved, just lost. For some components it happens to both of us.

I noticed others are experiencing a similar issue as well: UI Builder not Saving - ServiceNow Community

think you're running into an issue where UIB doesn't play nicely with source control currently. If your app is connected to source control, when one developer updates a record, the record is effectively "locked" until that developer commits their changes to git. In the classic environment, if you're not the developer who made the update, on a normal record you get a nice little message at the top letting you know what is happening and asking if you want to update it anyway and put developer B's changes into developer A's update set. UIB doesn't yet have that capability so the page is effectively locked with no messaging.