Dynamic Slot Values
I have a skill that looks up property management information for apartment buildings. We have over 150 properties which are defined as values for a slot. 4 digit property numbers for values and string property names as synonyms.
I would like to be able to query a database for the slot values and synonyms dynamically at runtime.
Thank you for submitting an Alexa Skills Feature Request. We are happy to inform you that the feature you have requested has launched!
You can read more on our blog: https://developer.amazon.com/blogs/alexa/post/db4c0ed5-5a05-4037-a3a7-3fe5c29dcb65/use-dynamic-entities-to-create-personalized-voice-experiences
Developer documentation can be found here: https://developer.amazon.com/docs/custom-skills/use-dynamic-entities-for-customized-interactions.html
This feature will be very useful. I have a similar situation where the choices change and it would be good to be able to build a dynamic list of values and match that to the user's request.
Chandrakanth Srinivas commented
Hi my slot values keep on changing how to update them dynamically or there are any other shortcuts like don't care slot values?
Mary Vo commented
Hi. I would also love the ability to source an api or database as I would like to create an Alexa skill for a card collection. This could be upwards to 20,000+ cards. It would be tedious to type every card as slot values.
Lisa Mabley commented
Are there any updates on this?
Ken Reiss commented
This would be an excellent improvement!!
Is it possible to create dynamic slots and intent using AlexSkillsKit dll and C# ? Could you please suggest on this.
Yes, this would be a great improvement.
My use case is like Robin's: I want to have a different set of slot values for each user, and these would change occasionally.
I would also love an API where I could update slot values (or just synonyms) in a custom slot type, without the need to go through the certification process - just to add more synonyms to a slot type that have continually been recognized by Alexa for a slot but have not been enough for them to be resolved in entity resolution.
Robin Jewsbury commented
This is really a very good idea. There lots of use cases where it helps. But my use case is there are >2600 train station names in the UK and many sound like each other. I'd like the user to choose typical usual station names when they enable the skill and then Alexa uses each user's personal slot list to understand the relevant station for that user.