UI Builder Custom Component property is not showing on UI Builder configuration
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-21-2024 03:44 PM
Hi there,
I have created a new custom UI Builder component and I have successfully deployed it to my instance (Vancouver). The component default value is showing however the configured Property is not showing on the component Configurations. I can see that the new Attribute is created on sys_ux_lib_component_attr but somehow it is not linked to the component? I am deploying it with --force so it dropes the existing and creates new component. Also, one more thing that I noticed that I have updated the name of the component rather than "My component" and the name is also not getting refelected e.g. still shows "My component"
@bradtiltonnow, I am following your article on here: https://developer.servicenow.com/blog.do?p=/post/quebec-nowexp-component-properties/
Has anything changed since then or it is a bug?
My component with property:
createCustomElement('x-293046-my-name-value-list', {
properties: {
keyValue: {
default: [
{ name: "Rahman Mahmoodi" , job: "Developer" },
{ name: "John Doe" , job : "Doctor" },
{ name: "Jane Doe" , job : "Nurse" }
]
}
},
view,
styles
});
now-ui.json:
{
"components": {
"x-293046-my-name-value-list": {
"innerComponents": [],
"uiBuilder": {
"associatedTypes": ["global.core", "global.landing-page"],
"label": "Rahman name-value table",
"icon": "document-outline",
"description": "A table that shows a JSON name value array as a table",
"category": "primitives"
},
"properties": [
{
"name": "keyValue",
"label": "JSON key value",
"description": "JSON array to be displayed as a table e.g. [{\"name\": \"Rahman\", \"job\": \"Developer\"}, {\"name\": \"John\", \"job\": \"Doctor\"}]",
"readOnly": false,
"fieldType": "string",
"required": true,
"defaultValue": "[{\"name\": \"Rahman\", \"job\": \"Developer\"}, {\"name\": \"John\", \"job\": \"Doctor\"}]"
}
]
}
},
"scopeName": "x_293046_my_name_0"
}
instance:
Attribute:
Any feedbacks will be appreciated
many thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
Hi Rahman4,
I'm encountering the same issue. Did you manage to resolve it on your end?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
I believe it was a caching issue or whatever for me. It appeared without me doing anything the next time I viewed the component. Try to clear the cache yourself and see if that resolves it.