Is faster for the app to create a slice filter or security filter..?
There really is no direct comparison when it comes to speed of creation. You are really comparing apples and oranges and which one you ultimately use depends on several factors.
Security Filters are levied on the server to only allow certain rows to be downloaded. They help by reducing overall app size but more importantly provide a security measure by not allowing data a user shouldn’t have access to. Security Filters don’t actually impact the app performance but they can impact Sync time if the filter expression is complicated - typically not a problem. Overall Sync time could be improved due to the fact there are fewer rows be delivered to the device.
Slices are created AFTER the data is downloaded and are simply a “different” representation of some table data. This could be reduced column size, reduced number of rows or both. Slices allow for segregation of data into smaller subsets which can help speed up certain pockets of processing - i.e. iterating over active Orders. But overall app performance is not really impacted by the use of a Slice and there is no impact to Sync time at all. If the app was sluggish before the Slice, it will still be sluggish after the Slice is created because all of the table data rows are still in the app and need to go through the same update processing they did before.
Security Filters in general are a better approach to filtering out data, and improving Sync time, as fewer rows in the app helps overall app performance - especially if it is a LOT of rows that are filtered out.
3 Likes
In italian we say “Grazie”. Top!
1 Like