- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-15-2022 01:38 AM
Hi All,
I have created a custom topic for Hardware related incident and I have created NLU Intents for this topic and configured necessary utterances. I have created one vocabulary source for list of all hardware and configured in the utterance. I created an mapped entity for this vocabulary source as well.
In the topic, I have used Reference Choice List property to fetch all related subcategory for Hardware from sys_choice table. I have used script to fetch the all these subcategory. Below is my code.
----------Code Starts-----------
getChoiceList: function(table,query){
var options =[];
var choices = new GlideRecord(table);
choices.addEncodedQuery(query);
choices.query();
while (choices.next()) {
options.push({
'value': choices.getValue('value'),
'label': choices.getValue('label')
});
}
return JSON.stringify(options);
},
Trying to test the topic.
When I am entering the keyword, it is predicting the correct topic and Hardware entity has correct value. But it is not mapping to the reference choice list.
Can someone please help me to understand why it is not mapping?
Thanks in advance.
Regards,
Hari
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-20-2022 12:59 AM
Hi Hariprakash,
The VA using the reference and static choice lists labels, not the values to match with the entity value. Please make sure that the entity values matching the choice labels.
Richard

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-20-2022 12:59 AM
Hi Hariprakash,
The VA using the reference and static choice lists labels, not the values to match with the entity value. Please make sure that the entity values matching the choice labels.
Richard
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-21-2022 11:00 PM
Thank you Richard for your answer. I found there is a space in the label. It is working now after we removed the space from it.