01-15-2018 12:46 PM
Hi,
I have a custom content model defined as below.
<type name="common:faqtest">
<title>FAQ</title>
<parent>common:basedoctype</parent>
<properties>
<property name="common:question1">
<type>d:content</type>
<mandatory>false</mandatory>
<index enabled="true">
<atomic>true</atomic>
<stored>false</stored>
<tokenised>true</tokenised>
</index>
</property>
<property name="common:answer1">
<type>d:content</type>
<mandatory>false</mandatory>
<index enabled="true">
<atomic>true</atomic>
<stored>false</stored>
<tokenised>true</tokenised>
</index>
</property>
</properties>
</type>
<type name="common:basedoctype">
<title>Content Model Base DocType</title>
<parent>cm:content</parent>
<properties>
<property name="common:locale">
<type>d:text</type>
</property>
<property name="common:effectiveDate">
<type>d:datetime</type>
</property>
<property name="common:expirationDate">
<type>d:datetime</type>
</property>
<type>
I have defined two properties - common:question1 and common:answer1 of type d:content. How do i retrieve these two properties using CMIS API? The properties are not shown in CMIS work bench also.
Basically we have a custom content model for FAQ. It used to have a question field and answer field. We set it to type d:text. Due to this, we cannot enter more than 1024 characters in the answer field. So we are trying to change the answer field data type to accommodate more text. Any suggestion?
01-15-2018 07:02 PM
The CMIS API as implemented by Alfresco does not support custom properties with type d:content. This is hard-coded in the implementation which always maps to the standard cm:content property.
01-22-2018 06:19 AM
Hi
The CMIS specification assumes a document has one bit of content and renditions of this content. See section 2.1.4.1.
As states you can not decide which content property this is - it is cm:content.
You can not redefine any mappings from the CMIS data model to the Alfresco data model - content to cm:content, name to cm:name, etc.
Andy
Explore our Alfresco products with the links below. Use labels to filter content by product module.