The attribute default value profile determines a default value for a feature. This is used when a feature is first created. It differs from auto calculation in that the user can change the value. It is only calculated when a feature is first digitised.

Profile variables

Variable nameTypeDescription
$mapFeatureSetCollectionThe list of layers in the web map. Can be used with the FeatureSetByName or FeatureSetById function to get a particular layer in the map. This can then be queried.
$userIdTextThe unique user ID of the editor who is logged into the application.
$userNameTextThe full name of the editor who is logged into the application.
$userIdentityTextProvides a credential instance. This can be used when accessing external layers with the FeatureLayer function. The credentials represent the user’s logged in credentials.
$sessionDictionaryA dictionary containing key value pairs. The dictionary contains all the session variables that have been configured in the app. When the application first launches, the user will be asked for values for the session variables. They can also (if configured) change session variables in the application. This provides programmatic access to the user’s choices / settings.
$editingLayerFeatureSetThe layer to which $feature belongs to. Can be queried to find other records.
$featureFeatureThe feature that has been edited, added or worked on.
$valueAnyThe value to test in the script. Certain rules, such as the restrict domain values rule, pass in a value for the current field value.
$parentFeatureFeatureIf there is a geographic contains relationship for the current feature being edited, this variable will contain the parent (or containing feature).
$routeFeatureFeatureIf the feature is a linear referencing feature, this variable will reference source route/line feature.

Return types

Date | Number | String | null
(depending on the type of field)

Example

Set the default value to todays date:

// Set the default value to todays date
return Now();