That's a bug in LINQ to Umbraco. It's because LINQ to Umbraco can't read properties which are stored as XML. Please vote for this issue: http://umbraco.codeplex.com/workitem/28731.
If you use the MNTP and store the data as cvs it should work.
Thanks for the quick reply Jeroes. I voted for this bug. The data comes from a custom control (http://ucomponents.codeplex.com/) and I don't want to change/recompile the control. What does MNTP mean ?
As Jeroen mentions, you can configure the Multi Tree Node Picker to hold it's values as CSV instead of XML, you need to change the selection in the datatype
uComponents - MultiNodePicker - LINQ serialization problem
Hello everybody,
I have a strange problem with the LINQ and the datatype MultiNodePicker from uComponents. The data stored by this control is in the following format
But using linq it returns 11021096116411661170.
I don't know if its a problem related to uComponents or umbraco.ling.
Have a good day
That's a bug in LINQ to Umbraco. It's because LINQ to Umbraco can't read properties which are stored as XML. Please vote for this issue: http://umbraco.codeplex.com/workitem/28731.
If you use the MNTP and store the data as cvs it should work.
Jeroen
Thanks for the quick reply Jeroes. I voted for this bug. The data comes from a custom control (http://ucomponents.codeplex.com/) and I don't want to change/recompile the control. What does MNTP mean ?
MNTP = Multi-node Tree Picker
MNTP means MultiNodeTreePicker. It's the datatype from uComponents you're using :). In the prevalue configuration of the datatype you can say how the value needs to be stored. See this for more info: http://ucomponents.codeplex.com/wikipage?title=MultiNodeTreePicker&referringTitle=Documentation
Jeroen
Thanks, I will convert my code to use CSV. But I hope this XML issue will be fixed in the next versions of umbraco.
Razvan,
As Jeroen mentions, you can configure the Multi Tree Node Picker to hold it's values as CSV instead of XML, you need to change the selection in the datatype
Rich
you got it already :)
This has been solved in Umbraco 4.6 because you can now also read xml properties with LinqToUmbraco :).
Jeroen
is working on a reply...