Don't walking` is not working on the remote table.

[Ariomar de Deus]

I created a remote table between the `sc_req_item` table and a custom table, but when using this remote table to create a list report, I can use `don't walking` but it returns empty. Could someone help me with whether `don't walking` is possible with the remote table?

[Naveen20]

Dot-walking on remote tables is defined but not resolved at report time — there's no real DB join, so dot-walked columns commonly return empty. You can try below

 

1. Reference column type = Reference, Reference table = sc_req_item
2. Your data-fetch script must push the sys_id of the sc_req_item record (not RITM number, not display value).
3. Recommended pattern: flatten the fields you need as their own columns in the remote table script (e.g., add cat_item_name) instead of dot-walking at render time.

• Community confirmation that dot-walking in remote tables is not supported in ServiceNow — Remote table in Dot walking
• Dot-walking error in the remote table — same author's earlier thread on the exact symptom
• Product Docs: Remote tables — official scope/limitations

[pavani_paluri]

Hi @Ariomar de Deus ,

In ServiceNow, dot walking works great on normal tables because the platform knows how to follow reference fields (like jumping from a request item to the user record and then to their department).

But with remote tables, that feature simply isn’t available. Remote tables are meant to pull in data from outside sources or custom integrations, and they don’t have the built‑in ability to walk across references the way native tables do. That’s why your report comes back empty when you try it.

No dot walking: You can’t just use sc_req_item.requested_for.email in a report if the base is a remote table.

Workarounds:
Add the extra fields you need directly into the remote table definition (for example, include the user’s email in the payload when you build the remote table).
Or, use a script in the remote table definition to look up related data and return it as part of the record.
If reporting is your main goal, sometimes it’s easier to use a standard table instead of a remote one, or enrich the data before it reaches ServiceNow.

Mark it helpful if this helps you to understand. Accept solution if this give you the answer you're looking for

Kind Regards,

Pavani P