Update a Custom Data Provider Feature Service

Once you have created a Feature Service that uses a custom data provider, you can update the underlying provider without removing the Feature Service.

Complete the following steps to update your custom data provider.

  1. In your development environment, make your changes to the custom data provider code, and export the custom data package as described in Build Custom Data Package.
    Do not attempt to modify and reuse an existing custom data package file (.cdpk). You should create a new one with the export command.

  2. Navigate to the ArcGIS Server Administrator Directory in a web browser, and sign in as an administrator.

  3. Click uploads > upload.

    1 2
  4. On the Upload Item page, click Choose File, and select your new .cdpk file. It is recommended that you provide a description in the Description text box to make it easier to distinguish between the new and old .cdpk. Before uploading the new .cdpk, you may alternatively delete the old one to avoid confusing the two.

    3
  5. Click the Upload button. Once the file is uploaded, you will be directed to a page with the following header: Uploaded item - <item_id>. Copy the item id.

    4
  6. Browse back to the root of the Administrator Directory and then click services > types > customdataproviders.

  7. On the Registered Customdata Providers page, click update. Now on the Update Customdata Provider page, paste the item id of your updated provider package into the Id of the uploaded item field.

    cdf arcgis server update provider page
  8. Click the Update button.

Now your feature service will be updated to use the latest changes you made to your custom data provider. Note that the update feature works by updating the provider by provider name. In order to update your provider, you must use the exact custom data provider name as you used on initial provider creation, and it must match an existing provider name.

;

Your browser is no longer supported. Please upgrade your browser for the best experience. See our browser deprecation post for more details.