지금 지원 담당자와 채팅
지원 담당자와 채팅

Migrator for Notes to SharePoint 7.4 - User Guide

Migrator for Notes to SharePoint Migrator for Notes to SharePoint Console
Overview Console configuration using the setup wizard Advanced configuration options Database discovery QuickPlace/Quickr discovery Domino.Doc discovery Discover directory entries Import database records Notes databases Applications Classification Rules Classification Rule Properties SharePoint Targets Scheduled tasks Reports Task history Link Analyzer/Updater/Finalizer License
Migrator for Notes to SharePoint Designer Migration jobs Appendix: Reference information

Generating XML documents

Migrator for Notes to SharePoint Document Generation feature allows you to generate XML documents and ASPX pages from Notes documents. This is accomplished by substituting elements in a "template" XML document that you provide with values derived from each Notes document being migrated. All the powerful data extraction capabilities of Migrator for Notes to SharePoint will be available here, including rich-text, attachments, dynamic @formulas for data conversion, multi-valued item handling, author name and access control mapping, versioning, and much more. The resulting generated XML documents can be saved into SharePoint as Document Library files, Form Library documents, List Item fields or Web Part Pages.

Generating InfoPath forms (pre version 5.2)

A common use for this feature is generation of InfoPath forms for use in SharePoint applications. Customers who are trying to replace existing Notes applications often build new InfoPath form templates that reproduce the dynamic behavior of their Notes form, such as hide-when formulas, computed fields and validation logic. These InfoPath form templates can be integrated in a variety of ways with SharePoint to create powerful document management, workflow and other compelling solutions. Migrator for Notes to SharePoint can rapidly migrate complex Notes documents to InfoPath forms for use with such solutions.

3
To generate repeating entries (an array) based on the values in a Notes multi-valued item, add the multi=‘repeat’ attribute to your <ppm:replace> tag. This will cause the surrounding XML tag to be repeated once for each input value encountered. You can also specify multi='repeatparent' to repeat the surrounding XML tag and its parent once for every value encountered in the multi-valued item. This option is useful for encoding multiple attachments (see below) or other repeating group elements in InfoPath.
To avoid generating tags when the Notes values are null, missing or empty strings, use the ifempty='remove' or ifempty='removeparent' attribute. This will cause the surrounding XML tag (or its parent) to only be generated if there is actual data in the source Notes item.
4
To generate rich text entries, add the encode=’xhtml’ attribute to your <ppm:replace> tag. This will cause the HTML markup extracted from your Notes documents to be saved into your generated document as XML tags rather than as plain text.
When using encode='xhtml' any Notes DocLink icons that are encountered are converted to encoded icons in your XML document. To disable this behavior, add the attribute linkicons=’false’ to your <ppm:replace> tag.  This will cause Notes DocLink icons to be replaced with a simple text link instead.
Other possibilities for the encode attribute are 'commonname' and 'abbreviatedname' for formatting Notes names and 'datetime', 'dateonly' and 'timeonly' for formatting XML Date/Time values.
If you wish the source data column to copied “as is” into the XML document, you can use encode=’xml’ rather than encode=’xhtml’. This might be useful if, for example, you have a Notes item that contains pure XML or you have created a formula column in your source data definition that emits an XML fragment. If you omit the encode attribute completely, the source data will be encoded as a Text element by default and any special characters (such as XML angle brackets) will be escaped.
To encode your attachment as an InfoPath attachment (using InfoPath’s proprietary format), add the encode=‘attachment’ attribute to your <ppm:replace> tag. To encode your attachment using standard base64 encoding, add the encode=‘base64’ attribute to your <ppm:replace> tag. This later choice is useful in some XML applications, but not for InfoPath.
To substitute target information in your XML, use the tag, <ppm:replace target=’site’>. Currently, the only supported value is “site” which yields the complete site URL.

Generating InfoPath forms (post version 5.2)

Generating raw HTML and XML

When using Migrator for Notes to SharePoint to migrate Notes rich text documents to SharePoint, the tool extracts your rich text "Body" item as HTML and map that to a SharePoint "Note" field (a multi-line text field supporting Enhanced HTML).

If you want to control how your HTML is encoded, Migrator for Notes to SharePoint supports the use of "pass through" HTML. If you want a string in your source data definition to be interpreted as pure HTML, set the Return Type to “HtmlString". For example, some custom Notes applications, especially web-enabled Domino applications, actually store raw HTML in text fields. Using the HtmlString return type can migrate those to SharePoint rich text fields "as is".

This is similar to the capability available when generating InfoPath XML documents from Notes documents. You can use the attribute encode="xml" inside your <ppm:replace> tags to indicate that you want the mapped source column to be treated as "pass through" XML.

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택