Association to child node of a data list

[peterzmlim]

Hi, I'm new to the datalist concept.

Basically I have nodes custom:docs that inherits "cm:content". I'm planning to use the data list to implement and maintain a list of clients "customcdl:clientList". This list will also be used as the data for a dynamic constraint list.

Now, it is mandatory for every custom:docs to "belong" to a client within the customcdl:clientList. Is it possible for the associativity to be done directly to the individual children of the customcdl:clientList?  Wouldn't <class>customcdl:clientList</class> associates the custom:docs node to the whole data list container? How can I directly associate to the child of the datalist of customcdl:clientList?

Also, as the client list is supposed to be available throughout the group without the user subgroupping of the Sites, is it possible to create the data list without the use of Sites?

Any help possible is definitely appreciated

Regards,
Peter Lim

[peterzmlim]

After further researching into datalistModel.xml, I've realized that customcdl:clientList that extends dl:dataListItem can be associated directly as dl:dataListItem is not the container but the child-node of the dl:datalist container that extends cm:content. I'm gonna try out the the associations.

But my other question still stand though, is it possible to create the datalist directly without the use of a collaboration site within Alfresco Share?

[mikeh]

But my other question still stand though, is it possible to create the datalist directly without the use of a collaboration site within Alfresco Share?

Absolutely. Remember that Share is "just" a remote UI tier which communicates with the Alfresco Repository via JSON-based REST APIs. Anything that Share can do can also be done either using Java or JavaScript code directly on the Repository, or by leveraging those same APIs in your own application.

Thanks,
Mike

[sbixsbix]

Hi, I am a newbie on Alfresco.
I have a such problem of this, I have a datalist i.e. "Branches", each item is composed by two fields "branch-code","branch-description"; then I have some documents with the property "branch-code".
I would to use the branch-code field of the datalist ad constraint for the branch-code in the document.
It would be great if the final user could scroll the the "branches" datalist with both the fields while inserting a new doc.
Any idea?