• System Information Options - Sets system-wide attributes
• Users and Groups - Sets attributes for a particular user or group
• Views - Sets both view and view access attributes
• Relationships - Sets attributes that define view relationships

1. System (such as user name, client version, etc.)
2. View
3. User
4. Record (when applicable)

• DS_USER - The name of the user associated with the connection (login user name).
• DS_DOMAIN - The domain the user logged on with.
• DS_APP - The name of the client application.
• DS_APP_VERSION - The version of the client application.
• DS_CURRENT_TIME - The current date and time for the DataSplice client or server.
• DS_EDIT_TIME - This will contain the initial time the record was edited, which makes things like time stamping offline modifications much easier.
• DS_VIEW - The name of the current view (if any).

• DS_AUTO_COMMIT - Specifies that record modifications are automatically committed when the record being modified loses focus (by clicking somewhere off the record). This can be defined system-wide, or for individual users and views. This works like the Records > Apply Record Changes menu item, which commits only the changes for the selected record. Any other record(s) in the modification history need to be committed with the Commit Changes button in the Remote Client application.
• DS_AUTO_INPUT_PANEL - Controls the automatic display of the SIP panel for views on Windows CE devices. This defaults to false. If set to true for a view (or system level), it will cause the panel to be automatically displayed when needed.
• DS_AUTO_RELOAD – Causes the view to refresh its displayed records whenever it is redisplayed by clicking the Back button in the Remote Client application. This is useful when two views are related in such a way that changing data in one view can affect the other view. In such circumstances, a view with this attribute will always display the latest data.
• DS_CLEAR_PASSWORD - Causes the client to remove the password from the input text field on disconnect. This is useful when multiple users access the same device. This attribute will supersede the value of DS_PERSIST_PASSWORD - i.e., the value of the latter will have no effect if the client is set to clear passwords.
• DS_DATE_FORMAT - The default date format to use when displaying date fields that do not otherwise have a format string defined. If no value is given to this attribute, the default format is %H:%M:%S %a, %b %Y.
• DS_DISPLAY_CLASS - Defines how record sets are displayed in the Remote Client. The following values are allowed:
  • grid - Default to grid display
  • vertical - Default to vertical display
  • grid_only - Only allow grid display
  • vertical_only - Only allow vertical display
• DS_HIDDEN_VIEW – Indicates that the view should not show in the client view list. This is useful for support views that are never accessed directly by the user. This attribute overrides any view class that might be present for the view.
• DS_MESSAGE_TIMEOUT - This attribute setting controls the maximum time the client will wait for a server response to any message (default: 60 seconds).

• DS_NO_COMPLEX_FILTER - Determines whether creating and editing complex filters is allowed for any user or view that has this attribute defined.
• DS_NO_FILTER - Boolean value that specifies whether viewing and editing filters is allowed for any user or view that has this attribute defined.
• DS_NO_OFFLINE - Specifies whether or not a user can get an offline session. This attribute can be set at the System or User levels.
• DS_PERSIST_DATA - This attribute is used to control whether the data for views is flushed when sessions are changed. If this is true, the client will retain the data for the view so it does not need to be re-downloaded by the new session.
• DS_PERSIST_PASSWORD - Specifies whether or not the Remote Client application should remember the last user's password along with the login name. This attribute can be set at the System or User levels.
• DS_PING_INTERVAL - This can be set to the number of seconds the client must be idle before a ping is issued prior to a new message being sent to the server (default: 30 seconds). If this is set to 0 a ping will be sent before each message. The drawback to setting this to a low number is that it will slow down the overall performance of the client, since each ping takes a certain amount of time to succeed.
• DS_PING_TIMEOUT - This controls how long the client will wait for a ping response before timing out and closing the connection (default: 5 seconds).
• DS_PURGE_CHANGES_ON_CLEAR – This will cause uncommitted changes to be purged from the device when users select Records > Clear Screen or when the clients disconnect.
• DS_RESET_CRITERIA_ON_SELECT – This will cause views to reset the last used criteria and fall back to the default criteria when navigating from the Select Views form.
• DS_SKIP_OFFLINE_UPDATE - Clients can now specify views to skip when fetching offline records. This can significantly speed up downloads with large, static views. This attribute controls which views are skipped by default. The first time offline records are requested, the DS_SKIP_OFFLINE_UPDATE attribute setting is not checked.
• DS_VIEW_CLASS - This defines view groups as different classes. This allows the client to categorize views when displaying views to select, such as only displaying views with a view class of Inventory.
• DS_WINDMILL_UPDATE – If set, the DataSplice Remote Client application can invoke the Windmill software update client, automatically detecting newer versions of installed software. This can be used at the System, User, or Group level.

To set a view's DS_DISPLAY_CLASS to single record mode:

1. Select DS_DISPLAY_CLASS in the Name dropdown list.
2. Select vertical from the Value column.

   

3. Click the Update button or change focus from the pane.

To create a custom view attribute that supplies a high-limit value in relation to measurement points along a route:

1. In the attribute's Name column, enter the name for the high-limit attribute, such as HIGH_LIMIT.
2. In the attribute's Value column, enter the default high-limit setting, such as 1000. Or, define the attribute as a query-based attribute by setting the value as follows:

           Query:
           view="Route Stops";
           field="High Limit";
           where="‘EQ Num’ = ${EQ Num} and ‘Point Num’ = ${Point Num}"
           

   For more information on query-based attributes, see the next section of this guide.

3. Click the Update button or change focus from the pane.

• view is the DataSplice view to query. View names containing white space should be quoted, e.g. view = "View Name";.
• field contains the value we are looking for. The field must match the corresponding field’s display name from the DataSplice view. If the display name contains white space, then the value should be quoted, e.g. field = "field display name";.
• where determines which row will match. Again, field references must match their corresponding display names, and any names containing white space need to be surrounded by double-quotes.

1. Our query attribute causes a lookup on the LOCATION_ASSIGNMENT view. The row having a TECHNICIAN value of SJohnson is found, and the corresponding LOCATION value (BldgF) is assigned to the attribute ASSIGNED_LOC.
2. Our mandatory view filter is applied so that the Work Order view only displays items for a location of BldgF.

Example:

    Query:
    view="LOCATION_ASSIGNMENT";
    field="Location";
    where = "Technician = ${DS_USER}";
    orderby = "Technician"
    

This would cause the results to sort by technician and the ASSIGNED_LOC attribute to get the value of the first row in the resulting set. In our example, the final value would be BldgA. However, the usefulness of this method is limited, since its results depend on the data in the underlying table.

When defining query-based attributes that reference field display names containing white space in the where section, the display name must be single quoted. If a display name in the where section contains white space and is not quoted, then DataSplice will interpret that as being two distinct objects and most likely the query will fail to return the expected result. It may even result in an error message.

    Query:
    view="LOCATION_ASSIGNMENT";
    field="Location";
    where = "‘Tech Group’ = ${my_group_field}";
    orderby = "Technician"