Requested Slot is filling with wrong values in X or SDK mode but its correct in Shell mode

Rasa version:0.11.1

Rasa X version (if used & relevant):

Python version:36

Operating system (windows, osx, …):windows server 2012

Issue: I’ve got very strange issue. I have a form that contains among other slots dwellingType_origin and dwellingType_destination. Either of them accept values like Elevator Building, Walkup Building and Private House. When requested slot is dwellingType_origin and a user puts Walkup Building this would fill dwellingType_destination and ask again for dwellingType_origin If user puts Elevator Building it will take it to the correct slot. I checked all my nlu and stories and made sure that it trained equally for all values for both slots But most strange thing is that when I use shell mode, it’s working correctly on all values! The problem occurs when I’m in X mode or SDK.

Error (including full traceback): doesn’t show error

**Command or request that led to error**:

**Content of configuration file (config.yml)** (if relevant):
```yml
# Configuration for Rasa NLU.
# https://rasa.com/docs/rasa/nlu/components/
language: en
pipeline:
  - name: "ner_spacy"
  - name: "SpacyNLP"
  - name: "SpacyTokenizer"
  - name: "SpacyFeaturizer"
  - name: "SklearnIntentClassifier"
  - name: "CRFEntityExtractor"
  - name: "EntitySynonymMapper"
  - name: "RegexFeaturizer"
  - name: "DucklingHTTPExtractor"
    url: "http://198.178.120.234:8000"
    locale: "en-US"


# Configuration for Rasa Core.
# https://rasa.com/docs/rasa/core/policies/

policies:
  - name: FallbackPolicy
  - name: MemoizationPolicy
  - name: FormPolicy
  - name: MappingPolicy


**Content of domain file (domain.yml)** (if relevant):
```yml

[emover]

Thank you for your response. However, this approach only works when the value of the answer can belong to 1 slot, such as cuisine, number_of_people etc. When value can belong to different slots, like in my case origin and destination, or in any other bot that has locations or time such as from and to, it doesn’t work In NLU it extracted based on context such as I’m going FROM nyc TO brooklyn. When it comes to filling the form and there is no context, it still trying to extract entity and fill the slot that is not in the requested_slot. Since nyc can be both origin and destination, the entity should not be extracted when the requested_slot is not empty but put the answer directly to the requeested_slot. But it doesn’t do it no matter what settings I’m using

On Thu, Jul 25, 2019 at 7:10 AM Vladimir Vlasov [e-mail] wrote:

yes, please see the documentation for slot_mapping: https://rasa.com/docs/rasa/core/forms/#custom-slot-mappings

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/RasaHQ/rasa/issues/4056?email_source=notifications&email_token=ABK7QWUB5XXAVEVKZTMWPCLQBGC2XA5CNFSM4IFOVU2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2ZFBZI#issuecomment-515002597, or mute the thread https://github.com/notifications/unsubscribe-auth/ABK7QWRG4SO44BMSSFUC5J3QBGC2XANCNFSM4IFOVU2A .

– Thank You, George Freed Software and web architect eMoverSoftware.com Phone: 2 <917-628-7030>12-537-6759

[Ghostvv]

the content of requested slot is a context, so you can customize for each slot how it can be filled in the order of importance, please see how form action uses slot_mapping: https://github.com/RasaHQ/rasa-sdk/blob/c6668354cee2a3ef2142cc257fa469911b182008/rasa_sdk/forms.py#L268

Since it is becoming a usage discussion I’ll close this issue. If you have more questions please check our forum: https://forum.rasa.com