Used by administrators to enable and disable certain administrative and performance features, this screen is accessed by selecting "Administration Properties" from the Web Part Administration drop-down menu. From this screen, administrators can also identify the types of lists, libraries and fields that can be moved, copied and mapped to each other.
If you select this option, only users with Administrator access will be able to access the Web Part Administration tools. By enabling this feature, you ensure that only administrators have access to modify any of the properties within the administrative panel. This prevents non-administrator users from erroneously disabling or renaming features or deleting special mappings.
The Data Publisher is a very powerful tool that can be very dangerous if used improperly. If you turn this option on, you can limit use of the Data Publisher to only those users who have been granted administrative rights. If this option is not selected, any user (except those with Read-only permissions) can use the Data Publisher.
This feature provides a user-friendly interface that makes it easy to build and apply filters for the data transfer. If this feature is disabled, users are required to construct filter strings manually. The Filter User Interface feature is enabled by default. For more information on using this feature, please see "Set a Filter" from the navigation to the left of this help topic.
When this feature it enabled, individuals with Administrator access can modify the look and behavior of the Data Publisher's menus. Five additional options will be included on the Web Part Administration drop-down menu (Break Menu Properties, Default Menu Properties, Drop Down Menu Properties, Hover Menu Properties, and Top Menu Properties; see DP: Menu Properties).
This setting only applies to copied records. When this setting is turned off and a copy is performed, only new records are added to the destination list or library; existing records in the destination list or library are not affected. When this setting is turned on, records are copied as follows:
When a record is created in SharePoint, it is assigned a unique ID. When the Data Publisher copies a record, it stores the ID of the source record in a field called CWDPOID in the destination record. This is the field that the Data Publisher references to determine whether or not a record in the source list already exists in the destination list the next time a copy is performed. The Data Publisher does not perform a field-by-field comparison.
If Overwrite Destination List Items is enabled when you perform a copy, the Data Publisher will determine whether the source ID exists in the destination list. If it exists, the record will be overwritten. If it does not exist, a new record will be created in the destination list.
NOTE: If you manually copy a record from one list to another, the source ID is not copied. As a result, the Data Publisher will not view that record in the destination list as a duplicate and it will create a new record.
When copying records between libraries, the Data Publisher does not check the source ID. Instead, it looks at the name of the attached file. If a record with the same file name already exists in the destination library and Overwrite Destination List Items is enabled, the record will be overwritten when the copy is performed.
NOTE 1: If a destination document library includes a look-up field and a library item is overwritten by a copy, you will lose the reference to the looked up item. You will need to access that record in the destination library and reselect the value.
NOTE 2: If you create a hardwired link to a document in the destination library and that document is overwritten by a copy, the link will need to be changed.
When enabled, the threading feature can provide your system with better overall system performance. It does not enhance the performance of the Data Publisher web part alone, but provides your overall system with better performance. If the Data Publisher is performing a large enough task, it can single-handedly tie up most of the resources your system has available. If you enable threading, the Data Publisher web part is allowed to run independently of the SharePoint web part queue and manage its own threads. This means that control will be returned to the SharePoint process more rapidly, allowing other web parts and web part pages to be rendered while the "expensive" Data Publisher is running.
If the Enable Threading option is enabled, this property sets the time limit (in seconds) that a thread can run before Data Publisher terminates it. This prevents web parts from holding up system resources for extended periods.
To avoid timing out, a browser needs to refresh itself
frequently. When the Enable Threading option is enabled, you can set the
Page Refresh Time to any value between 0 and 59 seconds to set the browsers
refresh interval while a process a running. This time interval represents
the amount of time in between each page refresh.
Example: If this property is set to 10, the current page will
refresh every 10 seconds for as long as the process is running.
This field defines all of the types of lists that you want the Data Publisher to recognize. Each list type entered here must be separated by a comma and contain no spaces.
Example:
If you wanted only Contacts, Events,
and Tasks lists to be made available in the Data Publisher, you would
enter: Contacts,Events,Tasks
The Data Publisher supports all list types except Surveys, Issues, and Discussions. The currently supported list types are:
Announcements
Contact
Document Library
Events
Generic List
Links
Picture Library
Tasks
XML Form
This field is used to define (map) the list types that can be selected as move/copy destinations. For each list type identified in "Allowed List Types," you must specify the list type(s) to allow as a destination. This property requires a special format to work correctly. If the list types are not mapped correctly, you will see not see any options available as a destination list when a primary source list is selected.
Format:
Source List Type=Destination List
Type,Destination List Type^Source List Type=Destination List Type,Destination
List Type
Example:
Contacts=Contacts,Events,Tasks,Announcements,GenericList^Events=Events,Contacts,Tasks,GenericList
This field is used to identify the library types that you want the Data Publisher to recognize. The name of each allowed library type must be separated by a comma (no spaces).
This field is used to specify the field types you want the Data Publisher to recognize when mapping fields. The name of each allowed field type must be separated by a comma.
Example:
MultiChoice,DateTime,User,Integer,Number,Choice,Note,Text
The Data Publisher supports the following field types:
Boolean
Choice
Cross-Project Link
Currency
Date/Time
Integer
Multi-Choice
Note
Number
Recurrence
Text
URL
User
Look-up fields and calculated fields are not supported. This is because the metadata for these fields includes information about other lists and fields from the source list that, once moved, would no longer match. The Data Publisher simply copies or moves field values; it does not recreate look-up and calculated fields in the destination list.
This field is used to define (map) the destination field types that can be selected as move/copy destinations. For each field type identified in "Allowed Field Types," you must specify the field type(s) to allow as a destination. If any field types are not mapped, they will not be available in the list of available fields for mapping in the "Define Data Transfer" step.
Each source field type must be separated by a carat ^ and each destination field type allowed for that source type must be separated by a comma (no spaces).
Format:
Source Field Type=Destination Field
Type,Destination Field Type^Source Field Type=Destination Field Type,Destination
Field Type
Example:
MultiChoice=Text,Note,MultiChoice^Choice=Text,Note,Choice^URL=URL
When you define the "Allowed Field Types" values as described above, you must take into consideration that there may be some system fields you do not want your users to see. The "Not Allowed Internal Field Names" field allows you to identify the internal field names of those system fields, so they will not be included in the list of available fields to be copied or moved. Place each internal field name in single quotes and separate each field with a comma (no spaces).
Example (these are the default values):
'ImageHeight','ImageWidth','_SharedFileIndex','_SourceUrl','HTML_x0020_File_x0020_Type','File_x0020_Type','Modified_x0020_By',
'Created_x0020_By','_ModerationComments','owshiddenversion','InstanceID','Order','CWDPOID','CWDPOLGUID','CWDPOSURL'
There are a few system fields, such as Modified, Created and Created By, that will exist in both the source and destination lists, but which cannot be mapped directly because the destination list must have its own unique values. If you want to copy or move these fields, an additional field with a different name must be added to the destination list. The "Appended Field Title" field allows you to define the text value that will be appended to the names of any of these fields.
Example:
If you specify "Original" as the Appended
Field Title and the user includes the Created By field in a copy, the
destination list will include a field called "Original Created By."
Data Publisher users can define text to be placed in an optional message field that is added to every record moved or copied to the destination list, or they can define custom text for the message field for individual records. The "Message Field Name" field is used to define the name of this field.
When you copy or move records, you can add a field to the destination list or library that provides a link back to the original source item. This field allows you to name the field that stores the link.