Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Data views

Updated on November 23, 2022

Use data views to bridge the connection between your application and the integration and to give your application the data the way the application expects to receive it.

Data views define the data associated with a data object and contain the data object's connection configuration to a system of record, separating your application from the integration with the system of record. Because of this separation, your application can easily adapt to integration changes and access data from a range of sources on demand. With data views, you can connect a data page of one object type to a data source of another, incompatible type, enabling data virtualization.

In App Studio you can view a list of data views associated with a data object, replace or update the source used by a data view, and configure its environment settings. Use App Studio to create data views, called data pages in Dev Studio.

Data views can be simulated, production ready, or not simulated and not production ready if the data view references a source that does not have settings that are configured for production. Simulated data views do not have a data source associated with them. You must configure the data source before the data view is ready for production.

  • Using data views in a case life cycle

    Use data views to access and use data that is not directly stored in your case. As a best practice, you can associate a data view with a data relationship to capture the connection between your case and a data view. By connecting a data relationship with a data view, you make your application easier to maintain. For example, you can view the data model to understand the relationships between each case and data object and quickly find which fields you want to reuse.

  • Data view errors in a case life cycle

    Help users resolve data view errors that they might encounter while they run a case. For example, you can present users with error messages that quickly guide them to a resolution with minimal disruption to the case.

  • Updating connection details and mapping for a data object
  • Updating connections and field mappings for a data source

    To keep connection details current, reconnect data views to a data source when connection details have changed. You can update existing connection details and field mappings, for example, if the authentication method has changed, or the schema of the data being sent has changed.

  • Preparing your data for production

    To avoid corruption of production data during development, create different environments for your data.

  • Simulating data

    To avoid development delays, use simulated data when a data source is unavailable.

  • Replacing a simulated data source

    To prepare your application for production, replace simulated data with the data from real data sources.

  • Turning on data source simulation

    If your data source is unavailable, you can continue to develop and test applications by turning on simulation for the data view (data page).

  • Turning off data source simulation

    Turn off data source simulation when you are ready to use your actual system of record.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us