Changes
XAML
,Created a functionality matrix for our different property filtering approaches (requested by customer)
</source>
==== UBIKPdfViewer ====
</tabs>
=== Advanced ===
* The [[XAML_Tips#SetPropertyValueCommand|Set Property Value Command]] sets a named property to a specific or calculated (such as through an [[EvalExpression]]) value.
== Commands ==
* ChildMetaDefUid: The Guid of the child meta definition to be used for creating the captured media document. If unspecified, the client will simply pick the first child meta definition that is of media type and is allowed under the current context/parent object.
== Object Filtering ==Filtering of objects is a common requirement in UBIK projects. The table below shows the three main approaches, with the functionality each offers. {| class="wikitable"! Type !! Configuration/Requirements !! {{Tooltip|Persisted|Filter criteria are retained when navigating, or even closing the client.}} !! {{Tooltip|Multiple/Complex Values|Multiple user inputs supported for a single filter property.}} !! {{Tooltip|Property type|Data elements supported as filter properties.}} !! {{Tooltip|Possible Item Source|Collections supported as item sources.}}|-| Query || Fully defined on the server || Yes || Limited (DateTime, Dbl, Int) where a range is possible. || Content properties only || Content objects, Documents|-| Property-Based Content Filters || Defined in XAML, requires custom [[Category:WinXSYSCLS_CHILDAREATEMPLATE|Child Area template name]] || Yes || No || Content properties only || Content objects only|-| Dynamic Filters || Fully defined in XAML|| No || Yes || Any bindable data (eg. Content properties, metadefinitions, etc). || Content objects, Properties, Documents, etc|-|} A [[Query]]is a container that delivers a defined collection of content objects. Properties can be added to the query to serve as filter criteria, where a user can perform their search by editing these properties. [[CategoryProperty_Based_Content_Filters]] are a xaml-based customization that connects a user input control (usually a textbox) with a specific property on the content object (the kind displayed in the Property tab of the mobile client). This user input is converted into filter criteria and applied directly to the child list, where only matched objects are retained. [[HowTo:XAMLImplement_Custom_Filtering|Dynamic Filtering]] is the most flexible, but also the most complex, method of XAML-based filtering. A set of [[EvalExpression|EvalExpressions]]converts user inputs into a complex filter string, which is then applied immediately to whichever ItemsSource is defined in the [[XAML_Changes_in_UBIK_WinX_3.5#Filtering_by_expressions|ListCollectionView]]/[[Xamarin_XAML#FeatureRelated|SfDataSourceExt]]. Note that in this approach, user inputs are not directly connected to any data, which means that reloading the page in any way (eg. by navigation) causes the input controls to return to their xaml-defined state. {{Attention|While any of the above approaches can be used, it is never recommended to mix approaches, as this causes multiple rounds of filtering per keystroke that will noticeably impact performance, especially when many objects and filters are involved!}}
== Miscellaneous ==
<br>
== Differences between Xamarin and UWP ==
{{Attention|Please consider that Xamarin.UWP is not an official product and therefore it can't be guaranteed that all our features work without issues.}}
== Namespace changes ==
