Scheduled Transfer
- Last UpdatedAug 14, 2025
- 2 minute read
The Transfer functionality is only available if there is a suitable database in the Multiple Database (MDB) (must be either the master or extract in extract hierarchies which only contains a single child extract). If no such database exists an error window is displayed.

Note:
There is no syntax for creating schedules, these have to be done using the Schedule Manager window.
When you have completed all task modifications to the item, you can transfer the modified item to the remote location.

Important:
The TRANSFER command will always FLUSH or REFRESH the latest state of the Database.
This means that any change to the database before the Scheduled Transfer-time will
become visible at the Transfer Location, although ownership of newly created items
will remain with the originator.
The Transfer Work window does not query the service to see what has already been scheduled. Feedback on Apply is only provided. If the Transfer Work window is closed (when you click OK) and re-opened, the Transfer items are generated from the current state of the Project databases without reference to already scheduled items.
The Transfer Work window displays all items in the Master or Extract that potentially can be transferred to the remote location. In the Transfer column select to toggle ON/OFF of the item that needs to be transferred, click Apply then OK (the OK button is temporarily disabled when you click Apply, as the selected items are being transferred). Selected items are sent to the scheduler to be transferred when the next schedule runs according to schedules defined by the Project Administrator.
Note:
If you close and opens the Transfer Work window the previously selected items are displayed OFF.
If you are transferring large projects and the projects fail to transfer, the following error message is displayed in the Event Viewer:
Message: There was an error while trying to serialize parameter http://Aveva.GlobalService/11.1/2010/11:results. The InnerException message was 'Maximum number of items that can be serialized or deserialized in an object graph is '65536'. Change the object graph or increase the MaxItemsInObjectGraph quota. Please see InnerException for more details.
Refer to Massive Base Product Projects for further information.