UIBuilder: "Component is not configured" error displayed when displaying form in Modal.

senon
Tera Sage

Hello, experts!

I am using UI Builder to create UI screens for my application.

 

■The requirements

I want to implement are Show the modal by pressing the button.
A modal displays a new record creation form for a specific table and a button to save that record.

find_real_file.png

■The problem

I'm having is that when I show the modal I get the error "Component is not configured Add details in the configuration pane" and the form and buttons are not visible.

find_real_file.png

 

■Here is what I have set.
・Creating a local data resource for [@servicenow/now-record-form-connected]>[GlideForm] to get form information.

find_real_file.png

・Create a button to open the modal.
To display the modal, specify the modal in the event handler [Open or close modal dialog (UXR Blank AppShell(To be deprecated))].

 

・Add a form and action bar components to the modal.

find_real_file.png

 

Best regard.

senon

3 REPLIES 3

Brad Tilton
ServiceNow Employee
ServiceNow Employee

I just replicated what you did in my San Diego instance where I added a modal with a form and action bar component and bound the gForm data resource to the three properties you show and it looks like it worked ok for me so I don't see anything wrong with your configuration based on the screenshots you've shared.

I would try clearing your browser cache or trying a different browser to see if that helps, and you might also try clearing the instance cache.

thank you for your reply.
I tried all the suggested methods but it didn't work.

The information I haven't provided is that this UI screen is created in a newly created application scope, not Global.

I presumed that the cause was the difference in scope, and when I made the same settings in the Global scope, my setting method worked.

It doesn't seem to work for certain application scopes. Any ideas what settings are missing?

Brad Tilton
ServiceNow Employee
ServiceNow Employee

I don't think it's scope related as my test was in a private scope (I never do anything in global) and UIB generally handles scoping pretty well. It may just be that it worked when you recreated it.