Updates features in a table by performing a query on a table using an MI SQL Update command string. In some cases the table will need a primary key column, depending on the data provider and the query. See the MapInfo SQL Language Reference for detailed information on MI SQL commands and functions.

ACL Authorization Flow

To update features in a named table by performing a query on a table using an MI SQL Update command string, the user (or any roles they belong to) will need Execute and Modify permissions on the named table in the following manner:

  • “EXECUTE” for entity type “Location Intelligence.Named Resources” for the user.
  • ”MODIFY” for entity type “Location Intelligence.Dataset.DML” respectively


Note: You must have View permissions on the named table as well as Create/Modify/Delete permissions on the named table's associated dataset to perform insert, update, and delete operations on writable tables. See Access Control for Datasets in the Administration section for more information.
Note: Update is supported on PostGIS, Oracle, SQL Server, SAP HANA, GeoPackage, and generic JDBC tables. It also supported on MapInfo native TAB and extended native TAB (NativeX) files on Windows operating systems only. Named tables with composite primary keys are not writable.

The following table lists the request and response messages for the updateBySQL operation.

Click on a message name to get more information about the message.

Message Description
UpdateBySQLRequest The request message for the updateBySQL operation.
UpdateBySQLResponse The response message for the updateBySQL operation.


Example request for updating features in a table using the MI SQL Update command with a bound parameter:

	<ns6:SQL>update "/MyTable" set ID = ID + 3, StringCol = 'Val' + (ID + 3), IntCol = (ID + 3) * @param1</ns6:SQL>
		<ns6:BoundParameter name="param1">
			<ns6:Value xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns2:IntValue">