I have a form in which I have slots which would use the same entities. If I make two separate entities for them and duplicate the data, it will become problematic as the NLU may classify “current_country” as “destination_country” and vice versa. Therefore I only use one entity, and try to map them in the slots_mapping function in my form actions. Example code: return { 'current_country': self.from_entity( entity='country', intent=['inform'] ), 'destination_country': self.from_entity( entity='country', intent=['inform'] ) } The problem with this is, since the intent is inform, it asks the first question: “What is your current country?” When I answer that, with lets say Estonia, it sets the value for both, current_country and destination_country, skipping the question for destination_country: What is your current country? Your input -> Estonia 2020-05-18 13:59:14 DEBUG rasa.core.processor - Current slot values: current_country: Estonia destination_country: Estonia requested_slot: current_country Obviously I want to be able to answer both questions separately, with separate values. Is there any way to do this cleanly through the slot_mappings? For example, something like this (pseudocode): return { 'current_country': self.from_entity( entity='country', response=['utter_ask_current_country'] # Only fill the slot on this response ), 'destination_country': self.from_entity( entity='country', response=['utter_ask_destination_country'] # Only fill the slot on this response ) } I’ve been trying different things and searching for solutions for hours, I’ve seen many similar questions, none of them have had a concrete answer. I’m not sure if I’m missing something, as I can’t believe something like this, which should be an extremely common usecase, doesn’t have any official coverage at all. Or is this the wrong approach for an usecase like this?

Yes,It loses NER capabilities. As I want to mention here It can be done in multiple approaches. For now I added logic in the required slots function so that it uses single entity to fulfill different slots Class CountryForm(FormAction): def name(self) -> Text: return "CountryForm" @staticmethod def required_slots(tracker: Tracker) -> List[Text]: """A list of required slots that the form has to fill""" if (tracker.get_slot('currentlocation') is None): return ["currentlocation"] else: return ["destination"] def slot_mappings(self) -> Dict[Text, Any]: return { "currentlocation": self.from_entity(entity="country", intent= "currentlocation"), "destination": self.from_entity(entity="country", intent="currentlocation") } def submit(self, dispatcher: CollectingDispatcher, tracker: Tracker, domain: Dict[Text, Any]) -> List[Dict]: current = tracker.get_slot('currentlocation') des = tracker.get_slot('destination') #Testing purpose dispatcher.utter_message("I am from {} and I want to go to {}".format(current, des)) return [] nlu.md ## intent:currentlocation - I am from [sweden](country) - I want to go [Estonia](country) - I am from [UK](country) - I am from [Russia](country) - I want to go [United States](country) - I want to go [sweden](country) - I want to go [UK](country) - I am from [Estonia](country) [3] [4]

Using a single entity for different form slots

Rasa Open Source

amn41 (Alan Nichol) May 20, 2020, 12:37pm 6

hi @Ulmm - I solved almost the exact thing in carbon bot using this new feature: Introducing entity roles and groups

Topic		Replies	Views
Custom map same entity to different slots in Forms Rasa Open Source	4	1039	June 25, 2020
Form and slots Rasa Open Source	12	615	August 14, 2022
Filling two slots , one with entity and one with whole sentence \| RASA Forms Rasa Open Source	1	970	July 10, 2020
Entities and Slots have same name Rasa Open Source	2	1371	March 19, 2019
Same training data for multiple entities issue Rasa Open Source	6	777	October 4, 2023

Using a single entity for different form slots

Related topics