2.5.2.6.5 Update a Business Connectivity Services Solution

  • Article

This use case describes how a client application can update a BCS solution published in the form of a list (1) on Microsoft SharePoint Server.

The following diagram illustrates this process.

Process for updating a Business Connectivity Services solution

Figure 19: Process for updating a Business Connectivity Services solution

Preconditions

  • BCS is enabled on the SharePoint site.

  • The client application can communicate with the SharePoint site.

  • The user has been authenticated and has read access.

Steps

  1. The protocol client initiates a request for updating a solution.

  2. The protocol server will verify the package existence and will verify that the external content type and the related external content types are current.

  3. If they are not current, the protocol server will generate a new package with the current external content type and the related external content types.

  4. The protocol server will return the package URL and the solution identifier to the protocol client.

Error

  • If an error occurs during the package generation process, the protocol server will return an appropriate error code to the protocol client.

Post-conditions

  • The solution package is accessible to the protocol client from a URL.

  • The solution identifier returned to the protocol client is different, indicating a newer version of the solution is available.

  • The solution package is not updated, because an error occurred during the package generation process.