Comments

# kwoodhouse said on November 4, 2006 3:55 AM:

I have loaded the current SharePoint server and client intergation components.  I have noted a number of items principally around hyperlinks:

1) If I have single map residing in a SharePoint doc library and select "edit" from the drop down all works well.  The map downloads to the "temporary MM SharePoint Directory" and the SharePoint Task Pane open in MM.  But, if I double click on the map in SharePoint the map appears to download to a temporary Windows directory and the task pane does not open.

2) If I have a hyperlink in file-1 to file-2, with file-2 also residing in the same SharePoint doc library, and activate the hyperlink in file-1, file2 appears to  download to a temporary Windows directory.  But the SharePoint task pane does not open in MM and the hyperlinks in file-2 are broken. Also, when saving file-2 in this scenario, the file is not saved back to the SharePoint doc library.

3) Given file-1 residing in a SharePoint doc library and opened by the "edit" from the drop down.  If you then perform a "send to" to create file-2 and then save file-2, the file save dialog does not default to the SharePoint doc library where file-1 exists.  This is at odds with MM behavior where the directory of "sent from file's location" is the default save location for a "send to" created map.

If you navigate from the save file dialog, which has its own SharePoint challenges, to SharePoint and save, the reciprocating hyperlinks in both file-1 and file-2 are broken.  

A related observations is that the SharePoint task pane in MM does not open for file-2.

Any correction or workarounds would be greatly appreciated as the net experience seems to rule out map-to-map hyperlinks and the regular "pruning" of maps that I used to with MM.

Thanks,

Kirk

Anonymous comments are disabled

About Michael S. Scherotter