embedded_list reference fields do not work
See original GitHub issueI have an edit view with an embedded list field that has sub-fields of reference type and they do not work properly. There is no call to the rest api asking for the list in this example.
nga.field('editResultsId', 'embedded_list')
.label('Edit Results')
.targetFields([
nga.field('fileSystemId', 'reference')
.label('File System')
.targetEntity(file)
.targetField(nga.field('name'))
.validation({ required: true }),
Issue Analytics
- State:
- Created 8 years ago
- Reactions:11
- Comments:20 (5 by maintainers)
Top Results From Across the Web
Regarding Reference Field in Embedded List - ServiceNow
The embedded list contains a reference field. ... Yes, by the time you open the record in the table, you dont have submit...
Read more >Embedded Data - Qualtrics
For a vast majority of users, embedded data field names are no longer case-sensitive, meaning “test” and “Test” would be treated as the...
Read more >List View formCompleting the Display Fields tab - Pega
Embedded ? Select if the output display of this list view is to appear within the run time presentation of another rule, such...
Read more >Reference fields | Mastering ServiceNow - Second Edition
Scripting, lists, and forms all understand references fields, as we'll see while we work through the chapters. Creating a reference field. Let's think...
Read more >Embedded lists Archives - ServiceNow Guru
... could show and hide an embedded related list on a form. I just created some client scripts to accomplish this task so...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I had a quick look at this today but wasn’t able to make much progress - had to figure out how things hang together. Leaving some notes as @etdev was keen to look at this also.
Crud/routing.js
creates a bunch ofui-router
resolve definitions based on the model coming out of theadmin-config
library.It looks like
lib/Utils/ReferenceExtractor
inadmin-config
is the culprit, it only looks at the top level object and doesn’t traverse complex fields.Took a quick stab at fixing this but I’ve run out of time to look at it this week and it doesn’t work. Here’s the code so far, it’s a recursive function to find all the reference fields during a call to
getReferences
.Cheers 😃
WORKAROUND – While waiting for the pull-request to be completed, I found an easy workaround. Just add the same reference field to your top level object (make it hidden, non-editable, not required). As long as you use the same object in .targetEntity() in both the top level and embedded, you will get a populated list. Below I just used an empty label and non-editable field, but you can use CSS to hide the field row as well.