Local Variables in Reusable Interface

That should not be happening in the first place. I am not sure what is the reason but to explain the interaction when you create local variables in that interface, the scope is limited to that interface only but when you call that interface in a new interface (parent) then you will be able to interact with the components and store their values in the child interface's locals and will also able to see them but cannot access them in the parent. If it made sense. 

Can you paste the code here for one of the child interfaces where you are facing this problem along with the parent?

I think I'm not allowed to post the original code, so I created an example with the same type of problem

Here is the parent:

a!localVariables(
  local!link: null(),
  {
    a!cardChoiceField(
      label: "Select A Version",
      data: {
        a!map(id: rule!IM_Child1(), icon: "globe-alt", primaryText: "Text"),
        a!map(id: rule!IM_Child2(), icon: "globe-europe", primaryText: "Num")
      },
      cardTemplate: a!cardTemplateBarTextStacked(
        id: fv!data.id,
        primaryText: fv!data.primaryText,
        icon: fv!data.icon,
        iconColor: "POSITIVE"
      ),
      saveInto: {local!link},
      maxSelections: 1,
      validations: {}
    ),
    a!sectionLayout(
      label: "",
      contents: local!link
    )
  })

Here is child 1:

a!localVariables(
  local!var:{"text1", "text2", "text3"},
  local!res:null,
  {
  a!dropdownField(
    label: "Dropdown",
    labelPosition: "ABOVE",
    placeholder: "--- Select a Value ---",
    choiceLabels: local!var,
    choiceValues: local!var,
    value: local!res,
    saveInto: {local!res},
    searchDisplay: "AUTO",
    validations: {}
  ),
  a!textField(
    label: "Text",
    value: local!res,
    labelPosition: "ABOVE",
    saveInto: {},
    refreshAfter: "UNFOCUS",
    validations: {},
    showWhen: a!isNotNullOrEmpty(local!res)
  )
})

Here is child 2:

a!localVariables(
  local!var:{"num1", "num2", "num3"},
  local!res:null,
  {
    a!dropdownField(
      label: "Dropdown",
      labelPosition: "ABOVE",
      placeholder: "--- Select a Value ---",
      choiceLabels: local!var,
      choiceValues: local!var,
      value: local!res,
      saveInto: {local!res},
      searchDisplay: "AUTO",
      validations: {}
    ),
    a!textField(
      label: "Text",
      value: local!res,
      labelPosition: "ABOVE",
      saveInto: {},
      refreshAfter: "UNFOCUS",
      validations: {},
      showWhen: a!isNotNullOrEmpty(local!res)
    )
  })

To recreate the problem you have to:

1. Select "Text" choice.

2. Choose any value in dropdown.

3. See nothing has changed.

4. Switch to "Num" choice.

5. Switch back to "Text" choice.

6. At this point I obtain the "Text" interface with refreshed variable.

Your child interfaces need to actually save their values up into the parent interface.  I'm not altogether clear what you're doing in this example exactly, but it's pretty clear to me that no value ever gets saved from the child to the parent.  In both of your child interface examples here the local variables are scoped such that they'd only be accessible locally.

There's not some sort of "magic" that makes data in a child interface automatically promote up to a parent interface, you actually have to build that into your structure.

Your child interfaces need to actually save their values up into the parent interface.  I'm not altogether clear what you're doing in this example exactly, but it's pretty clear to me that no value ever gets saved from the child to the parent.  In both of your child interface examples here the local variables are scoped such that they'd only be accessible locally.

There's not some sort of "magic" that makes data in a child interface automatically promote up to a parent interface, you actually have to build that into your structure.