The Location lookup is not rendering

[RohitN244878896]

When I click on the location lookup it is not rendering and it is stuck like the screenshot shown below. It is not showing up any data for long time

And I am getting like below only when I remove the dependent field company from dictionary

[LohitakshS]

Hey Rohit,

Run into this one a fair bit — a blank lookup that just hangs is usually one of three things. Quick way to narrow it:

1. Pop open DevTools (Console + Network) and click the magnifier again. If you see a JS error, it's a front-end render problem. If you see an XHR just sitting there, it's a slow or failing query on the back end.
2. Check the reference qualifier and ACLs. Your typeahead is also throwing "Please select a value..." — so it's not just the modal, nothing's coming back at all. That points at the data source. Run the Location field's qualifier in a background script and make sure read ACLs aren't quietly blocking the records.
3. If it's an extended table or a page variant, the variant can break the link between the field and its lookup modal — opens fine but never loads. Worth comparing your sys_ux_macroponent modal/lookup child screen against a working OOB page.

Rough rule: stuck spinning → it's #1 or #2 (a heavy/hanging qualifier). Opens totally blank with no spinner → probably #3.

Share what the console spits out and I'm happy to help you trace it.

[RohitN244878896]

This is what I can get from network and console when I click on location lookup

[LohitakshS]

That helps. Everything's 200 and nothing's hanging, so it's not a slow back-end query. Looks more like a front-end render thing.

Quick test: a couple of those (macroponent_drivers, the df0efa… script) are loading from the Polaris service worker cache, not the network. A stale cached driver makes a lookup open but never load. Try the same record in incognito — if it works there, it was just a bad cache.

Also heads up, a 200 doesn't mean success here — exec and the xmlhttp.do call can return 200 with an error in the body. Worth peeking at the Response tab on those.

Two things that'd help: flip to Console, filter Errors, click the lookup again and send whatever red shows up. And does it break on a fresh incident too, or just this one? That Location value's already flagged invalid, so it might just be dirty data on this record.

[RohitN244878896 · Accepted solution]

Once dependent field - company is removed from Location dictionary the issue is resolved. And additionally for the hierarchy format we need to make the tree_picker attribute as false. If it is true it will show like in the picture mentioned