Listing child properties in a parent node datatype?
Is it possible to list one or more properties' values of all child nodes under a parent node? It seems reasonable that a custom datatype could achieve this with an SQL call or similar.
here's my example:
Lest say I have a child page that has a property called "Calibration" which could be a date or textstring or whatever works. I've created 10 or 12 child pages, each with different values in this property.
Now the parent page is more or less a container. If a user is to go into the content manager to change the calibration on each of the child pages, it would be easier / faster if they could go down the list on the parent node and change them from one location.
You might want to use the embedded content package or the uComponents Data Type grid to do this. Instead of using child nodes, you could have all that information in that "parent" node.
@dan - what i have is a set of properties entered into each child page. the parent page lists all the child page's properties in a grid. so, it looks good from the from end.
@Sébastien - the reason for this is each child page is a stand alone sensor with more properties. I probably would have gone that route if it were one just property. I wanted to be able to add and remove sensor pages as needed. Unless I'm mistaken with embedded content, I would be exchanging - removing single sensor pages with removing each property from multiple embedded content tabs.
maybe it's possible to be able to make it so a logged in member can edit those properties on the front end? seems unlikely or unsecure, but i'm open to suggestions.
Yeah on the front end you would have 100% control, just need to wire it up approprietaly. But with either embeded content or uComponents data type grid, those "child elements" would in fact not have a landing page of their own on your site, but you could make it so that their parent displays it approprietaly. With these advanced data types you can add remove sort each element, so should be alright in that way. Maybe I'm not understanding your context clearly enough though, but give it a try on local dev you'll see right away if it fits.
Listing child properties in a parent node datatype?
Is it possible to list one or more properties' values of all child nodes under a parent node? It seems reasonable that a custom datatype could achieve this with an SQL call or similar.
here's my example:
Lest say I have a child page that has a property called "Calibration" which could be a date or textstring or whatever works. I've created 10 or 12 child pages, each with different values in this property.
Now the parent page is more or less a container. If a user is to go into the content manager to change the calibration on each of the child pages, it would be easier / faster if they could go down the list on the parent node and change them from one location.
Any Ideas?
You might be able to achieve this on the front end side of umbraco. On the backend I have never seen this before.
You might want to use the embedded content package or the uComponents Data Type grid to do this. Instead of using child nodes, you could have all that information in that "parent" node.
@dan - what i have is a set of properties entered into each child page. the parent page lists all the child page's properties in a grid. so, it looks good from the from end.
@Sébastien - the reason for this is each child page is a stand alone sensor with more properties. I probably would have gone that route if it were one just property. I wanted to be able to add and remove sensor pages as needed. Unless I'm mistaken with embedded content, I would be exchanging - removing single sensor pages with removing each property from multiple embedded content tabs.
maybe it's possible to be able to make it so a logged in member can edit those properties on the front end? seems unlikely or unsecure, but i'm open to suggestions.
Yeah on the front end you would have 100% control, just need to wire it up approprietaly. But with either embeded content or uComponents data type grid, those "child elements" would in fact not have a landing page of their own on your site, but you could make it so that their parent displays it approprietaly. With these advanced data types you can add remove sort each element, so should be alright in that way. Maybe I'm not understanding your context clearly enough though, but give it a try on local dev you'll see right away if it fits.
is working on a reply...