Flow "... is not a valid dot-walk for record"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-12-2025 10:47 PM
Hello there folks!
I am working on a Flow that handles the request process of a TRM Record. When doing the process, I get an error after approving it, instead of the product being created (Screenshot 1).
In reviewing the logs, I could tell that the error seems to be in some reference to the “sys_domain_path” field. The full log message:
Operation(TRM Software Product Request F failed with error: com.snc.process_flow.exception.InValEvaluationException: sys_domain_path is not a valid dot-walk for record sn_apm_trm_product_request
I'm stuck as apparently we have two Flows that take care of this (image 2). And going through all the Flow actions one by one, I can't find any reference to this field. Any idea what could be the error? or how can I find this reference in my Flows that are causing the error?
I can add more images of what you think is necessary to solve this. Any help is appreciated!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-12-2025 11:07 PM
is your flow working fine but throwing that error?
where did you see that log?
Seems your flow is trying to set a dot walked field
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-13-2025 09:02 AM
Correct, the Flow works, but when approving the request, instead of creating the TRM Item (as it should) it sends me this error.
I checked the log in the System Logs filtered with all the logs that have “Flow” as source.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-04-2025 07:17 AM
Hi Aram,
If it helps you, I have the same issue, and saw this KB :
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1005124