Skip to main content

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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Best practices for data modeling

Updated on April 5, 2022

Follow best practices to save time developing and maintaining your data model.

Use the following data modeling guidelines:

Getting started

  • Reuse data objects by promoting a built-on data object or copying the assets from a standard Data- class.

  • If your data source is unavailable, connect your data objects to simulated data in local storage.


  • Repurpose data views instead of creating new ones when your system of record changes.

  • Update data sources created in App Studio in Dev Studio only when necessary because some changes made in Dev Studio make the rules uneditable in App Studio.

    For more information, see Updating connections and field mappings for a data source.


  • Actively remove the data objects and fields that you do not use.

  • Provide transformations to automate post-import changes to your data.

  • Maintain separate environments for development, staging, production, and testing.

  • Save import settings as a template to avoid manually mapping fields during future data imports.

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