Multi-Category Ancestry Rules
5 posts by 2 authors in: Forums > CMS Builder
Last Post: February 24, 2011 (RSS)
The way that categories work is one of the things I like best about CMSB. I particularly like the way that you can work with the hierarchy via the various Parent/Ancestor/Descendant rules.
The only fly in the ointment is that in order to establish such a category hierarchy all records must be part of the same table - administered by the same Section Editor. (This is a limitation which continues to bug me, as one size does not fit all!)
What I want to know is if it's possible to set up the same hierarchy relationship between different tables/categories?
I know, in principle, it's possible to assign any record to any category - simply by creating a drop-down menu system, etc...
What I want to know is can we do it in such a way as to maintain the ancestry rules?
:0s
Perchpole
The only fly in the ointment is that in order to establish such a category hierarchy all records must be part of the same table - administered by the same Section Editor. (This is a limitation which continues to bug me, as one size does not fit all!)
What I want to know is if it's possible to set up the same hierarchy relationship between different tables/categories?
I know, in principle, it's possible to assign any record to any category - simply by creating a drop-down menu system, etc...
What I want to know is can we do it in such a way as to maintain the ancestry rules?
:0s
Perchpole
Re: [Perchpole] Multi-Category Ancestry Rules
By Jason - February 22, 2011
Hi Perchpole,
Do you mean breaking up the hierarchy structure across several tables? Or do you mean having the hierarchy structure in one table and then associating records in other tables?
The latter can certainly be done. If you want to be able to see the structure in the dropdown in the other section, use the breadcrumb field as your label value.
Does this help answer your question? If not, could you please give an example of what you are trying to do?
Thanks
Do you mean breaking up the hierarchy structure across several tables? Or do you mean having the hierarchy structure in one table and then associating records in other tables?
The latter can certainly be done. If you want to be able to see the structure in the dropdown in the other section, use the breadcrumb field as your label value.
Does this help answer your question? If not, could you please give an example of what you are trying to do?
Thanks
---------------------------------------------------
Jason Sauchuk - Project Manager
interactivetools.com
Hire me! Save time by getting our experts to help with your project.
http://www.interactivetools.com/consulting/
Jason Sauchuk - Project Manager
interactivetools.com
Hire me! Save time by getting our experts to help with your project.
http://www.interactivetools.com/consulting/
Re: [Jason] Multi-Category Ancestry Rules
Hi, Jason -
Thanks for the response.
I suppose I mean breaking up the hierarchy structure across several tables.
In effect, I want to make a record from Table1 the parent of a record in Table2 (and so on....)
I assume the current category hierarchy set-up is hard-wired into CMSB. I just wondered if we could mimic it somehow and yet retain the ancestry.
:0/
Perch
Thanks for the response.
I suppose I mean breaking up the hierarchy structure across several tables.
In effect, I want to make a record from Table1 the parent of a record in Table2 (and so on....)
I assume the current category hierarchy set-up is hard-wired into CMSB. I just wondered if we could mimic it somehow and yet retain the ancestry.
:0/
Perch
Re: [Perchpole] Multi-Category Ancestry Rules
By Jason - February 23, 2011
Hi Perch,
You can create a field called "parent" in a section and associate it with a record in another section. In the "parent" section you could also use a related records field to show "children". This is just a way of emulating a parent/child relationship. You wouldn't have a way of return a hierarchical structure of records using this.
If you could give an example of when you would need to do this, we may be able to suggest a different approach.
Hope this helps
You can create a field called "parent" in a section and associate it with a record in another section. In the "parent" section you could also use a related records field to show "children". This is just a way of emulating a parent/child relationship. You wouldn't have a way of return a hierarchical structure of records using this.
If you could give an example of when you would need to do this, we may be able to suggest a different approach.
Hope this helps
---------------------------------------------------
Jason Sauchuk - Project Manager
interactivetools.com
Hire me! Save time by getting our experts to help with your project.
http://www.interactivetools.com/consulting/
Jason Sauchuk - Project Manager
interactivetools.com
Hire me! Save time by getting our experts to help with your project.
http://www.interactivetools.com/consulting/
Re: [Jason] Multi-Category Ancestry Rules
Hi, Jason -
Thanks for your feedback. I appreciate it's not an easy one. I suspect I'll have to approach the problem from a different angle...
:0)
Perch
Thanks for your feedback. I appreciate it's not an easy one. I suspect I'll have to approach the problem from a different angle...
:0)
Perch