> For the complete documentation index, see [llms.txt](https://docs.migration-center.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.migration-center.com/3.17-update-3/release-notes.md).

# Release Notes

## migration-center 3.17 Update 3

This release is a collection of cumulative fixes that have been done since version 3.17 Update 2.

{% hint style="info" %}
For updating from version 3.17 Update 2, only the Jobserver component needs to be replaced. There are no updates to the MC Client and MC Database components.
{% endhint %}

### Fixes

* Veeva Importer:
  * Importing submission to Veeva RIM with skipUploadContent throws error but import is successful (#60418)
  * Importing submission with skipUploadContent checked does not work (#60306)
  * Uploading/Downloading content to/from FTP Staging Folder does not work with REST calls (#60493)
  * Setting object\_type\_\_v attribute throws NullPointerException (#60659)
  * Updating objects throws an error (#60571)
  * The version tree is not correctly scanned when the minor version is greater than 9 (#60957)
  * Submission response is not parsed correctly (#60780)
* Veeva Scanner:
  * Veeva scanner continue working on background after stop (#60805)
* SharePoint Online Scanner:
  * Scanning objects throws an error when parsing the creation date (#60751)
  * An SQL Exception is thrown when the attribute value is greater than the limit (#60208)
  * The build sometimes is compiled for 32 bit platform (#60211)
  * The total number of objects displayed in summary is not correct (#60205)
* D2 Importer:
  * NullPointerException when importing VD relation updates (#60470)
* Dctm Importer (NCC)
  * Updating content on Documnetum NCC with ECS does not work properly (#60795)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.migration-center.com/3.17-update-3/release-notes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.