Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Migrator for Notes to SharePoint 6.16 - 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

Generating InfoPath forms (pre version 5.2)

Previous Next


Migrator for Notes to SharePoint Designer > Generating InfoPath forms (pre version 5.2)

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.

To generate XML documents
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' you can also add an 'images' attribute. This is similar to the 'src' attribute in that it should be the name of another source data definition column. The images are encoded right into the XHTML and you go not need to migrate them separately.

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.

You can control the name of generated XML files by mapping a dynamic source column to a FileName field in your target data definition.

Generating InfoPath forms (post version 5.2)

Previous Next


Migrator for Notes to SharePoint Designer > Generating InfoPath forms (post version 5.2)

Generating InfoPath forms (post version 5.2)

To generate InfoPath form documents from Lotus Notes documents that were created using Notes forms

With some form templates, the XSN importer cannot determine what the HREF (location of template) should be for a generated document. For instance, if a template was imported into Central Admin, approved by an administrator, then assigned to a site, where SharePoint automatically created a content type for it. In this case, the published XSN location is not in the XSN. For these unusual cases, you need to specify the template location in the Published XSN location field. This field will be automatically loaded with the location if the XSN importer can determine the HREF.

Once an XSN has been loaded using the ‘Load XSN’ link, the ‘Export XSN’ link is enabled. Clicking ‘Export XSN’ launches a file save dialog box, allowing you to save the previously-imported XSN back to a file on disk.

The Map InfoPath template fields dialog also includes a complete list of the available Mappable Fields, which are the parts of the generated InfoPath form documents that you might want to map Notes data to. If desired, you can customize how these Mappable Fields appear on the Mapping tab. Recall that Migrator for Notes to SharePoint maintains the distinction between the reusable Target Data Definitions that describe the schema of your SharePoint targets and the mapping of source columns to target fields in a specific migration job. You can clear certain Mappable Fields that you do not want to show on the Mapping tab. You can also override some of the Mappable Field properties such as the MappableName that is visible on the Mapping tab and the AutomapNames property that provides a hint as to which Notes source columns should automatically map to the target field.

If you import a form template (.xsn) with two leaf nodes having the same name, the MappableNames fields are pre-filled with a fully-qualified path to the node in the tree (that is, Customers/Customer/name). This prevents duplicates in the target documents.

If a field is inside a field that is repeating, it's Multi property will be auto-set to ‘RepeatParent’. All sibling fields must have this property set to ‘RepeatParent’. This prevents the parent element from being repeated in the generated XML.

You may wish to enable the "Migrate Attachment Icons" feature in your migrated InfoPath form documents. This will allow the original attachments icons in Notes to appear in SharePoint.

Once you save your Target Data Definition, the various parts of the InfoPath Document field you defined will be available on the Mapping tab. A special "Field.Part" notation is used here. In the example, we called the InfoPathDocument field "Doc" so the mappable parts are called "Doc.Body", "Doc.Title", "Doc.Status" and so on. There is also a special field called "Doc.FileName" that allows you to set the names of the generated InfoPath files from dynamic Notes data

When you run the job, Migrator for Notes to SharePoint will generate one InfoPath form document for each Notes document. You can inspect the migration log for any issues.

Generating raw HTML and XML

Previous Next


Migrator for Notes to SharePoint Designer > Generating raw HTML and XML

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.

Generating read-only HTML

Previous Next


Migrator for Notes to SharePoint Designer > Generating read-only HTML

Generating read-only HTML

When using Migrator for Notes to SharePoint to render Notes documents as HTML, the Notes fields for radio buttons and check boxes become editable in the output since the generated HTML documents are not read-only. To disable editing of radio buttons and check boxes, set the HTML output to read-only.

To generate read-only HTML:

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation