Publish changes between environments

Use environments to safely update your apps and pipelines before you release those changes to users. Each publish applies a full update of your entire solution.

Make changes in Development

Use the Development environment to modify schema, like:

• Creating new tables and fields

• Updating forms and reports

• Modifying pipelines

To access Development resources directly from the My Apps page or Pipelines, or from Solutions:

1. Navigate to the Development environment page.

2. Select the app or pipeline you want to update.

3. The resource opens in a new tab so you can update the structure of an app or pipeline. Live data is not included in the Development and Testing environments.

Your changes remain in the current environment until you choose to publish them.

Avoid editing Production directly

Do not make schema updates directly in Production.

Editing Production directly can cause conflicts between environments. These conflicts may result in:

• Production changes being overwritten during the next publish

• Development changes failing to publish due to schema conflicts

• Incompatible object IDs between environments

• Permanent data loss in affected tables or fields

Because environments rely on consistent schema alignment, changes made outside the Development → Testing → Production flow can break that alignment.

To prevent conflicts, we recommend things like:

• Make all structural changes in Development

• Promote changes forward through environments

• Avoid manual schema updates in Production

Publish changes to the next environment

To publish changes to another environment:

1. Finish making your changes in an app or pipeline.

2. In Solutions, return to the environment page.

3. Select Review changes. The review modal may take a few minutes to load the changeset. Once it loads, you can:

   1. View added, updated, or removed items

   2. Search within the changeset

   3. Expand specific apps, tables, or pipelines to understand what changed

   Use this view to confirm that the updates are complete, accurate, and ready to move forward. Learn more about limits to reviewing changes.

4. After you review the changes, select Publish.

   Your solution is locked while changes are published, meaning you can’t make additional changes.

Publishing moves your updates to the next environment or directly to users, depending on your setup. You cannot publish a single app. All apps and pipelines in the solution publish together.

Limits to reviewing changes

There are a few known limits and issues in the Review changes modal. We’ll continue to develop this feature throughout the beta.

• Pipeline structures may not expand correctly when modifications are present.

• Rich Text page content is not rendered correctly.

• The changeset may display the AllowDataCopy property even when no actual changes have been applied.

• Phantom changes may appear in the changeset for legacy forms that contain rows with a single element.

• Some objects may be marked as changed despite no actual modifications.

• The changeset does not display changes for RoleDefaults and ReportOverride options.