Tutorial: Update Databases Using an FME Flow Workspace App

Toyosi Akinselure
Toyosi Akinselure
  • Updated

Introduction

FME makes it easy to update your database, either through a single feature edit or bulk edits. Once published to FME Flow, FME Flow Apps allow you to share FME workflows with anyone, no FME Flow account is required. This enables users to easily make changes to the database, even when in the field. This tutorial covers three different databases: Oracle, Microsoft SQL Server, and PostGIS, and could be modified for other databases. For each database, two scenarios are demonstrated:

  1. Bulk edits: This bulk insert is useful when you anticipate a large number of edits being made so that FME Flow does not get tied up with multiple calls. Instead, data is pushed to FME Flow in groups.

  2. Single feature edits: Respond to single feature database edits and push features individually. This is good when you have a low volume of individual edits.

 

Requirements

  • Externally Accessible FME Flow

  • FME Workbench

  • Access to Oracle, Microsoft SQL Server, or PostGIS.

 

Articles

Bulk Edits:

Bulk Edits Oracle

Bulk Edits SQL

Bulk Edits PostGIS/PostgreSQL

 

Single Edits:

Single Edits Oracle   

Single Edits SQL

Single Edits PostGIS/PostgreSQL

 

Additional Resources

Data Attribution

The data shown here originates from open data made available by the City of Vancouver, British Columbia. It contains information licensed under the Open Government License - Vancouver.

Was this article helpful?

We're sorry to hear that.

Please tell us why.

As of January 14th, 2026, comments on knowledge base articles have been closed. To make sure questions don’t get missed and to enable more community support, we’ve moved discussions to the FME Community. If you have a question or a comment about this article, please create a new post or create a support ticket.