TMCore SharePoint Module 3.0 Known Issues, Fixes and Workarounds
TMCore SharePoint Module 3.0 Known Issues, Fixes and Workarounds
This blog entry is used to record and document known issues found with the TMCore SharePoint Module version 3.0 and their current status.
If you discover an issue with the TMCore SharePoint Module that is not listed here, then please report it to us at support@networkedplanet.com.
Ref. | Issue | Resolution |
---|---|---|
690 |
Cannot connect to SharePoint site from the NPCL editor. When using the NPCL Editor Extensions provided with the TMCore SharePoint Module to map topic types in the ontology to content types, you may be presented with a log-in dialog to connect to the SharePoint site to retrieve a list of content types or field types. If you are connecting to the SharePoint site as a domain user, the dialog requires a domain and user name to log in, you must enter this full log-in name in the form domain/user, rather than the more usual domainuser form. NOTE: From Hotfix 4 for the TMCore SharePoint Module, this fix will be included in the installation package. |
Workaround: Enter your log-in name in the form domain/user. |
685 |
ASP.NET Error when attempting to enable List Auto-classification When using the link from a List Settings page to enable Auto-classification on the list, you may encounter the following ASP.NET error: Multiple controls with the same ID 'ctl00$PlaceHolderMain$ctl05$ctl01$RptControls$EnableAutoClassification' were found. Trace requires that controls have unique IDs. This error message is caused because two different elements of the NPClassification feature accidently use the same Id value. To fix this on an existing installation, follow these steps on each server in the server farm:
NOTE: From Hotfix 4 for the TMCore SharePoint Module, this fix will be included in the installation package. |