Skip to main content
simranj0886
Participating Frequently
February 23, 2023
Solved

DataSource Naming Best Practice Info

What is the best practice for naming a datasource in Appian?

In DEV, UAT, PROD can what should be the name of datasource be provided?

    peter.lewis
    peter.lewisAnswer
    Employee
    February 24, 2023

    Sure, we document that right here: https://docs.appian.com/suite/help/latest/Appian_Administration_Console.html#data-sources

    The key phrase is: "If you are using multiple environments, a data source with the same name must be created in each environment."

    View in thread

    9 replies

    abhayd3663
    abhayd3663
    Brainy
    February 24, 2023

    This page provides standard Appian design objects and object property naming conventions that you can adapt to your environment and organizational guidelines as needed.

    kaushikm0002
    New Participant
    February 24, 2023

    Best practice for naming all the objects is defined here - Standard Object Names - Appian 22.4

    simranj0886Author
    Participating Frequently
    February 24, 2023

    Thank you [mention:5ad3e26073a44ed083578c6ba0906265:e9ed411860ed4f2ba0265705b8793d05]  [mention:2089375b23b7421da3e660bd7c7ae972:e9ed411860ed4f2ba0265705b8793d05] my concern is related specific to the data source naming conventions.

    For e.g. Appian DEV has a datasource configured with name as "sample-dev-db01" where as the datasource name in Appian UAT is configured as "sample-uat-db01" due to which every time the deployment is happening the datastore entity need to be added manually and then all the constants pointing to the datastoreEntity need to updated manually!

    Hence I want a guideline on the datasource configuration in different environments and what is the Appian Best Practice? I couldn't find in any of the best practices/standards shared by Appian.

    peter.lewis
    peter.lewis
    Employee
    February 24, 2023

    I'd recommend keeping the same name for the database in each of your environments. It's already implied that it will go against the dev/uat/prod version of those, so naming it more about the business purpose (e.g. Case Management DB) will generally be easier to work with.

    simranj0886Author
    Participating Frequently
    February 24, 2023

    Dear [mention:6b9f80ff18f9420082d13ef2d5121d56:e9ed411860ed4f2ba0265705b8793d05] Thank you for your input. I would really appreciate if you can help me in pointing out any documentation for the same?

    Terms & ConditionsAccessibility statement