Many resources, such as views, procedures, and Web services, are dependent on one or more underlying resources. Dependent resources are considered ‘bound’ to the underlying resources. Imported resources often need to be bound again in their new location.

Binding a resource to its dependencies is also often necessary in the import process. For example, a procedure P1 might retrieve data from table T1 in the development data source DS1, and refer to it accordingly in its FROM clause. In this case, P1 is said to depend on T1, and P1 and T1 are said to be bound. When importing P1, the user must ensure that the connection to T1 is fed from either DS1 or another data source—for example, a live production data source rather than a QA or development data source.

For additional information, see Rebinding a View and Rebinding a Procedure.

Exported resources are often bound to underlying sources, and the binding should be reestablished (or changed) when the resources are imported.

When a resource is marked as rebindable in the CAR file, Studio import of this resource displays the path and description in a dialog box that lets the user specify a new path for the dependency resource.

Or