The TabSelector approach shown above only works with the default tab set (Children, Properties, Documents). If a tab is added, removed, or reordered, this default mechanism can no longer be relied on. The example below shows how a customized tab can be preselected in such cases, without losing the functionality of the TabSelector.
{{Hint|TabSelector is an enum (index 0 -> ChildrenTab, index 1 -> PropertiesTab, index 2 -> DocumentsTab). In the Mobile Client, tabs are selected by their position in the list, which equals the enum index, starting from 0 (0, 1, 2, ...), which only matches the enum index in the default tab set. So Once tabs are added, removed, or reordered, the Expression needs to translate each TabSelector value into the tab's actual position of in the matching tabcurrent layout, as shown in the example below. UWP matches tabs by name instead, so no such mapping is needed there.}}
<tabs>