Hey, this is a great addition... loving it so far... my thought is this... and here is the scenario...
I use the Embedded Content dataType to specify CREATE product categories on the products Home node.
i have a folder off the tree for bulk products when i create a product, i would love to have a categories checkbox, dropdown, whatever that pulls from the embedded content datatype on the Productes Home node.
The major difference between using this control and actually adding sub nodes is that there are no 'nodes' created in the backend (with versions etc), the umbraco.config Xml which is otherwise created from the raw data is in this case created directly and saved with the data on the nodes, or in other words: the created Xml is not backed up by any other data. If you just operate on the Xml (cached) data, there isn't really any difference between using this control and sub nodes. However if you operate on the actual data behind the Xml you won't find anything other than Xml.
That was a bit complicated for what I actually want to say: if the other control (checkbox, dropdown, whatever) operates on the actual data then you won't have any luck unless you change the way it operates, if however it operates on the Xml representation that shouldn't really be a problem. E.g. you could list all name fields of embedded items from sub nodes of 'home' with "/home/*[@isDoc]/{your-property-alias}/data/item/name". However when I tried anything like that with the uComponents: XPath CheckBox List control it didn't even like to save the xpath expression, so maybe I'm doing something wrong with the xpath or we'd need an answer from the author I guess.
Hope that makes sense and answers your question a bit,
Embedded Content companion?
Hey, this is a great addition... loving it so far... my thought is this... and here is the scenario...
I use the Embedded Content dataType to specify CREATE product categories on the products Home node.
i have a folder off the tree for bulk products when i create a product, i would love to have a categories checkbox, dropdown, whatever that pulls from the embedded content datatype on the Productes Home node.
any thoughts?
Hi bob,
The major difference between using this control and actually adding sub nodes is that there are no 'nodes' created in the backend (with versions etc), the umbraco.config Xml which is otherwise created from the raw data is in this case created directly and saved with the data on the nodes, or in other words: the created Xml is not backed up by any other data. If you just operate on the Xml (cached) data, there isn't really any difference between using this control and sub nodes. However if you operate on the actual data behind the Xml you won't find anything other than Xml.
That was a bit complicated for what I actually want to say: if the other control (checkbox, dropdown, whatever) operates on the actual data then you won't have any luck unless you change the way it operates, if however it operates on the Xml representation that shouldn't really be a problem. E.g. you could list all name fields of embedded items from sub nodes of 'home' with "/home/*[@isDoc]/{your-property-alias}/data/item/name". However when I tried anything like that with the uComponents: XPath CheckBox List control it didn't even like to save the xpath expression, so maybe I'm doing something wrong with the xpath or we'd need an answer from the author I guess.
Hope that makes sense and answers your question a bit,
cheers, Sascha
Hi Sascha,
I'm a big fan of this datatype and use it a lot in my personal projects. I was wondering if you had plans for a update for version 5 ?
Many thanks!
Mike
is working on a reply...