accessing custom properties with JavaScript

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

paullewon

I have a custom aspect defined as follows:

    <aspects>
      
      <aspect name="cu:sourceInformation">
         <title>Source Information</title>
         <properties>
            <property name="cu:sourceTitle">
               <type>d:text</type>
            </property>
            <property name="cu:imprint">
               <type>d:text</type>
            </property>
            <property name="cu:mcode">
               <type>d:text</type>
            </property>
            <property name="cu:isbn">
               <type>d:text</type>
            </property>
            <property name="cu:isbn13">
               <type>d:text</type>
            </property>
         </properties>
      </aspect>
     
   </aspects>‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

  
And I have a .ftl for pulling properties as a pipe-delimited output as follows:

<#list folder.children as child><#if child.isDocument>${child.name}|${xmldate(child.properties.modified)}|${child.properties.description!""}|${child.properties.creator}|${child.properties["cu:isbn"]}<br /></#if></#list>‍

It works with everything but the last ${child.properties["cu:isbn"]} reference, which is the only custom property in it. When I add that custom property reference I get the following error:

Error during processing of the template 'Expression child.properties["cu:isbn"] is undefined on line 1, column 172 in propertysheet.get.html.ftl.'. Please contact your system administrator.

I've tried quite a number of syntax variations on that reference. What am I missing?

Thanks,

Paul

kevinr

FreeMarker is very strict on 'null' values - if that property does not exists on a document and returns 'null' it will cause that error I think.

I've not tried the syntax you are using, but you have something similar for 'description':
${child.properties.description!""}

which i assume means to display "" if the value is missing i.e. null. Can you try something similar for the 'cu:isbn' value?

We normally use the ?exists built-in to filter out missing values.

Thanks,

Kevin