IDM

Using IDM with Microsoft SharePoint as the content repository

When using IDM with Microsoft SharePoint as the content repository, there are several limitations to the solution. The limitations are (bold indicates changes since last version):

  • No free text search (documents or attributes). Clients are dynamic and do not show the free text search tab if there is nothing to free text on.
  • Using Microsoft SharePoint on multiple user domains is not supported.
  • No support for multiple site collections (1 Server equals one site collection in Microsoft SharePoint).
  • Data model translations are only supported for one language, meaning that Infor delivers English translations, but customers can change this to their language of choice.
  • ACLs are supported and work by moving documents from a root folder with specific access rights to another root folder with possibly different access rights. In this way, it is possible to change a document’s access restrictions.
  • Control Center Configuration Exporter does not support Document Types or Value Sets.
  • Control Center Configuration Importer does not support Document Types or Value Sets.
  • Collection attributes have limited support.
  • Collections with one column are supported.
  • Collections with more than one column are not supported. Transactions are not supported, thus you cannot perform several operations in one transaction and then do a commit or rollback as with other IDM editions.
  • Not all XQueries are supported.
  • Versioning – Only major versions are used, 1.0, 2.0, and so on. Microsoft SharePoint supports minor versions such as 1.1 and 1.2. IDM will conform to these versions but always create major versions for new versions created in any IDM client or API.
  • The unique identifier, PID, has a different structure. The different structure is Guid_Guid_Guid_int (WebId_ListId_ItemId_Version). Any software that has persisted PIDs to documents in IDM must verify that this different format can be handled.
  • There are Microsoft SharePoint attribute types that are not supported by IDM. They are: Choice, Calculated, External data, Look up, Read only, and User/Group.
  • Search operators – “Not Like” is not supported. “Like” is handled as “Contains”; no wild cards are supported.
  • Default attribute "Name" and the Original Filename must be unique within the same folder. The original filename is calculated to the BaseName attribute in SharePoint, which is used by default as the Display Name in IDM and thus given the name “Name” in IDM clients. IDM will calculate a new name if a conflict occurs unless you are forcing the name by using the API. Then you will get an error.
  • The maximum search result is 5000 (same as Microsoft SharePoint clients). Thus, you cannot access search results beyond that limit. To do so, you must add more search criteria to limit the search result.
  • Using Microsoft SharePoint Foundation and MS SQL Server Express will limit the database size. This affects the possible size of a solution that can be operational using Microsoft SharePoint Foundation edition running on MS SQL Server Express.
  • Document libraries in SharePoint that contain the "/" character are not supported. They will be filtered out and never visible in any IDM client.
  • BaseName (Name") is a computed field from the org filename. Thus, when searching with "=" (equals), you must include the extension to get a match. Using "LIKE" or "CONTAINS" when searching to get a match can produce additional unwanted results.
  • “localhost” is not supported for use in connections.
  • File size is restricted to 100 MB for each file. By default, Microsoft SharePoint is set to a limit of 50MB, but you may increase this. However, going above 100MB will not help since the 100MB limit is strict in IDM.
  • A “Multi-value” attribute type (an attribute that can hold more than one value) cannot be edited in Microsoft SharePoint clients, only in IDM clients/API.
  • With multi-value attributes, you can use only the “=’ and ‘LIKE’ operators.
  • Filename of the actual file is a unique value in SharePoint and must be unique. The filename is set by setting the built in “Name” attribute in SharePoint. Thus the Name attribute must be unique if provided; otherwise, IDM will generate it for the user. The uniqueness is enforced within a folder, and since a folder in SharePoint represents an ACL in IDM, that also means that a filename must be unique within an ACL.
  • Cache synchronization available in the IDM Control Center may require a refresh of data in Microsoft SharePoint.
  • Value sets are not available in the IDM Control Center.
  • Document types are not available in the IDM Control Center.
  • Trailing spaces will not make an attribute’s value unique.
  • Not able to sort by Checked out date or Document Type in client.
  • Attribute level permissions are not available.
  • To enable Document Templates, customers should manually add the MDS_TemplateName and MDS_TemplateDetails attributes to the Document Types that they want to enable for Document Template usage.
  • The Delete BOD is not supported.
  • Only the Delete action is supported. A Retention_Policy_User user must be available. This user name cannot be configured.
  • Infor Ming.leTM Chat will not work on PostgreSQL before 9.5.