Changes
/* Preselection of customized Tabs */
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, ...). So the Expression needs to translate each TabSelector value into the position of the matching tab, as shown in the example below. UWP matches tabs by name instead, so no such mapping is needed there.}}
<tabs>
Add an EvalExpression evaluating the tab index, and bind it to the TabView SelectedIndex:
<source lang="xml">
<!--
If the Title of the context object is 'MyObjectTitle', tab index 1 (Custom Tab) should be selected.
Otherwise, if the TabSelector enum name is ChildrenTab, tab index 0 (Children Tab) should be selected.
And if the TabSelector enum name is anything else (PropertiesTab or DocumentsTab), tab index 2 (Properties Tab) should be selected.
-->
<controls:EvalExpression
x:Key="CustomTabSelector"
<tabView:SfTabView SelectedIndex="{Binding Source={StaticResource CustomTabSelector}, Path=Result}">
<!-- tabView:SfTabItems in the order Children Tab (index 0) / Custom Tab (index 1) / Properties Tab (index 2) ... -->
</tabView:SfTabView>
</source>
