Scenario 1: Committing New or Full FE Scripts

The Forward Engineer Schema Generation Wizard generates a physical database schema or Forward Engineering (FE) script. For a Mart Model, you can push the FE script to a Git repository.

To commit new or full FE scripts to Git repositories, follow these steps:

  1. On the ribbon, go to Mart > Open.

    2. The Open page appears.

  2. Select a model, and then click Open.

    3. The Mart Model opens.

  3. Go to Actions > Schema.

    4. The Forward Engineer Schema Generation Wizard appears.

  4. On the Forward Engineer Schema Generation Wizard, click the Preview section.

    5. The FE script appears. For example, in the following image the Preview section displays FE script of a Databricks database. For more information on generating FE scripts, refer to the Forward Engineering/Schema Generation for Databases topic.

  5. Click .

    6. The Commit to Git screen appears.

  6. Enter appropriate values in the fields. Fields marked with an asterisk () are mandatory. Refer to the following table for field descriptions.
    7. Field Name Description Additional Information
    Connected To Specifies the connection that connects erwin DM to a Git repository For example, ConnectGit.
    Git Repository Specifies the Git repository configured for the connection

    For example, https://gitlab.com/d4215/GitLabIntegration is set for the ConnectGit connection.

    This field autopopulates based on the repository configured in the Git Connection Manager.
    Git Branch Specifies the Git branch configured for the connection

    For example, main is set for the ConnectGit connection.

    This field autopopulates based on the repository configured in the Git Connection Manager.
    File Name Specifies the user-defined name of the FE script file being committed to a Git repository

    For example, Databricks-Sales-Data.sql

    To avoid script files from being overwritten, ensure that you use unique file names.
    Git Path Specifies the location in the Git repository where the FE script is committed

    For example, FY2022/

    The FE script is committed to the FY2022 folder inside the root folder of your Git repository.
    Commit Summary Specifies the summary of the push commit For example, Sales Rectification.

    Author Name

    Specifies the name of the author pushes the commit

     

    Author Email ID

    Specifies the email address of the author pushes the commit

     
    Local Path Specifies the location on your local machine where the FE script is saved C:\Users\SO\Documents\Databricks
  7. Click Commit.

    8. The FE script file is saved on the local path and committed to the Git repository.

    For example, in the following image, FE script is committed to a GitLab repository in a file, Databricks-Sales-Data, with a commit summary, Sales Rectification using the main branch.

    You can click the file to review its content. For example, in the following image, Databricks-Sales-Data's content is visible.

You can use FE Schema Generation Wizard to commit FE script using the same connection again. The Commit to Git screen autopopulates the previously set values in File Name and Git Path.

For example, in the following image File Name is set to Databricks-Sales-Data and Git Path is set to FY2022/.

Committing the FE script again with the same File Name and Git Path overwrites the previous file in the Git repository.

Once the FE script is committed, you can run it on your database to generate and verify the physical schema.

For example, in the following Databricks database, the FE script copied from the Git repository is run.

After running the FE script, the required database objects are created. You can access these objects from the database. For example, the following tables can be accessed in a Databricks database.