Skip to main content




Service Studio version:

Data Action

  • Edit
    Collaborate with us
    Edit this page on GitHub
  • Use Data Actions to fetch complex data from the database or external systems after the Screen loads. Data Actions run on the server.

    Data Actions and client-side Aggregates concurrently start to fetch data after the Screen loads.

    Don't perform login operations in Data Actions expecting to use the GetUserId() function in its On After Fetch event. The parallel execution of Data Actions and client-side Agreggates in a Screen overrides the session authentication cookie. Using the GetUserId() function in the On After Fetch event might return an empty value.


    Name Description Mandatory Default value Observations
    Name Identifies an element in the scope where it is defined, like a screen, action, or module. Yes
    Description Text that documents the element. Useful for documentation purpose.
    The maximum size of this property is 2000 characters.
    Server Request Timeout Maximum time in seconds to wait for the Data Action to return data before triggering a Communication Exception. Overrides the default timeout defined on the module.
    Fetch Yes At start
    On After Fetch Action executed after the aggregate fetches data from the data source.

    Runtime Properties

    Name Description Read Only Type Observations
    IsDataFetched True when data has been fetched from the database and is ready to be used. Yes Boolean
    HasFetchError True when there is an error during data fetch due to a server error or communication timeout. Yes Boolean
    • Was this article helpful?