×
Menu
Index

Content

Content
1

Content Type Name

1. Content Type Name
Specifies the content type name.
2

Content Type Caption

2. Content Type Caption
Specifies the content type caption.
3

Default

3. Default
Specifies the default content type. When the program sends a record to SharePoint, the program searches for which content type to send. If the program finds more than one content type, the program will use the content type that has been set as Default, otherwise user will have to choose the correct content type.
4

Type

4. Type
Specifies the type of content type.
  • Record - is that standard type that is used for record metadata or document metadata.
  • Document Set - is the type that is used for document sets only.
5

File Name Template

5. File Name Template
Specifies the template for the naming of files that are created from templates on SharePoint via NavSherpa on Card/NavSherpa Smart Tree (NavSherpa)/Create File From Template. This field accepts constants or Text variables.
6

Parent CT Site Setup Code

6. Parent CT Site Setup Code
Specifies the Parent Site Setup Code which contains the parent content type to be used when creating new content types. This is used only with the Update to SP command.
7

Parent Content Type Name

7. Parent Content Type Name
Specifies the Parent Content Type Name to be used when creating new content types. This is only used with the Update to SP command.
8

Sorting

8. Sorting
Specifies the sorting of content types in the SmartTree.
9

Automatically Replace files

9. Automatically Replace files
Specifies if to automatically replacement files. If a file has the same name as an existing file, the existing file will be overwritten by the newest file version with the same name.
10

Force Document Names By Template

10. Force Document Names By Template
Specifies whether the file name will be changed during uploading documents to the SmartTree via Content/File Name Template.
11

Transfer To List Setup Code

11. Transfer To List Setup Code
Specifies the "SharePoint List Setup" to be used as the destination when data is copied. This can be used for documents.
 
Example:
A "Sales Order" is posted and a "Posted Sales Invoice" is created. The "Sales Order" is deleted and the relation is lost. If a list on SharePoint is used as sales document and needs to maintain a relation after posting, a copy function is used to transfer the mapping from the "Sales Order" to the "Posted Sales Invoice". More information on how to use retain relations is available via How to implement NavSherpa functions to Events.
12

Transfer To Cont. Type Name

12. Transfer To Cont. Type Name
Specifies the destination content type name to be used during transfer.