Notes Migrator for SharePoint has the ability migrate Notes documents to InfoPath data documents.  As described in previous posts [link], this feature currently requires hand-editing an XML template file.  It is one of the more complicated parts of the product and, frankly, it is all to easy to generate an XML document that InfoPath does not like.  We will be making all this a lot easier in an upcoming patch release, but meanwhile some debugging tips are in order. 

The best way to resolve almost any problem here is to create a sample InfoPath document directly in your SharePoint document library and compare it line-by-line to an InfoPath document generated by Notes Migrator for SharePoint.  To download the XML data documents to your local hard disk, right click on the documents in question in your document library and select the Send To -> Download a Copy action.  

Now use a tool such as the freely available WinMerge [link] to compare the GOOD and BAD docs.  Once you get good a ignoring the data differences and focusing on the structural differences, this process will usually help you spot the problem quickly.

Here are two examples that came from a real-world support case:

PROBLEM:  Some of the radio button fields on my InfoPath form do not show the values from my Notes documents.

SOLUTION:  I see a number of cases where the GOOD document is storing an alias and the BAD document has a string.  For example in the DrinkingWaterSource field, InfoPath is using “2” instead of “City Supplied Water”.  The remedy is probably to use a formula in Notes Migrator for SharePoint to convert the Notes values what InfoPath expects.  Or change the InfoPath form design to allow text fields.

PROBLEM:  The Attachment button does NOT work on the records created by the tool.

SOLUTION:  The BAD example does not include the <?mso-infoPath-file-attachment-present?> tag.  It is harmless to have that even if you don't really need it, so be sure to add it to your XML template.