I've got 5 different DAMP data types, I cannot figure out why it loses its values (setting like root node, allowed extensions basically every single information for DAMP data type)
the preserve value is false
preserve="false"
my question is that should I add Damp data types to PreservedPreValues or MatchedPreValues?
I would try matched - (i haven't tried this for DAMP - but it's how MNTP works)
with matched pre values usync tries to ensure that the order of the prevalues is kept (for most datatypes this doesn't matter) it generates slightly more db traffic, but might be the answer.
that could be true - when you export / import a datatype, you don't always get the values written out to the xml in the order they are stored (it's a bit odd) so when using matched types usync checks sort order too, to make sure it reads and writes in the order they are stored in the DB - this means it can sometime work and sometimes not -
exactly the behaviour we where getting with MNTPs which made me write the matched types stuff.
yes - you need to add the GUID that is written as ID in the xml file (sorry not at a pc now - can't tell you what that is for DAMP) once that is done, all DAMP doctypes will use matched.
it shouldn't matter in terms of DB - uSync is using the umbraco api - can you post the usync xml for the damp controller (its in usync/datatypes) ? also just confirm the file contains the same settings (or which ones are missing) from the xml
I will do some checking to see if i can replicate it.
Just to be 100% clear, when you talk about putting the GUID in the matched prevalues area, you are talking about using the ID GUID instead of the Definition Guid?
That sounds great! We are using umbraco 6.1.6 and have usync 1.5.8.2 installed via nuget. I don't see the 1.6 on nuget. Is it possible to get that version from nuget?
DAMP Data Type losing its value
Hi
I am using Umbraco 6.1.6 with uSync 1.5.2.
I've got 5 different DAMP data types, I cannot figure out why it loses its values (setting like root node, allowed extensions basically every single information for DAMP data type)
the preserve value is false
my question is that should I add Damp data types to
PreservedPreValues
orMatchedPreValues
?Any help is much appreciated.
Thanks
Ali
I would try matched - (i haven't tried this for DAMP - but it's how MNTP works)
with matched pre values usync tries to ensure that the order of the prevalues is kept (for most datatypes this doesn't matter) it generates slightly more db traffic, but might be the answer.
Hi Kevin,
Not all the DAMP data types loses its value, it is vary sometimes is 2 out of 5 sometimes 1 out of 5.
couldn't really figure out any sort of pattern so far :(
Thank you
that could be true - when you export / import a datatype, you don't always get the values written out to the xml in the order they are stored (it's a bit odd) so when using matched types usync checks sort order too, to make sure it reads and writes in the order they are stored in the DB - this means it can sometime work and sometimes not -
exactly the behaviour we where getting with MNTPs which made me write the matched types stuff.
what would you suggest shall I add it to MatchedTypes?
yes - you need to add the GUID that is written as ID in the xml file (sorry not at a pc now - can't tell you what that is for DAMP) once that is done, all DAMP doctypes will use matched.
so it's something like
with the key being the ID Guid - the value doesn't actually matter it's just so you can spot it in the config.
sure thanks will do it and let you know
cheers
Ali
Hi Kevin,
Have tried that but no luck :( it is still the same.
can it be because we are using different database?
Cheers
Ali
Kevin,
Is there anyway to exclude DAMP Data Type from uSync or I need to exclude all data types?
Cheers
Ali
it shouldn't matter in terms of DB - uSync is using the umbraco api - can you post the usync xml for the damp controller (its in usync/datatypes) ? also just confirm the file contains the same settings (or which ones are missing) from the xml
I will do some checking to see if i can replicate it.
thank you ! here is the xml file
Just to be 100% clear, when you talk about putting the GUID in the matched prevalues area, you are talking about using the ID GUID instead of the Definition Guid?
In the case above would you use:
and you would not use:
Thanks
Hi yes its the ID (at least i think it is)
the xml is a bit confusing because the ID is the ID of the underling datatype, not the ID of this particular type - that's in the definition !
Awesome. I just confirmed that. The ID is the underlying ID and the Definition is the specific definition for that Data Type.
Thanks!
if you are still using umbraco 6.1.6 - you should also try the latest version of uSync from here
https://github.com/KevinJump/jumps.umbraco.usync/tree/v1.6.x-inheritiedObjects/Package
the 1.6 version has had significant work on it, and does lots more checking and importing now - and works better with things like DAMP pickers.
That sounds great! We are using umbraco 6.1.6 and have usync 1.5.8.2 installed via nuget. I don't see the 1.6 on nuget. Is it possible to get that version from nuget?
https://www.nuget.org/packages/uSync/
Huh. I just thought I'd try anyway. I typed:
and it worked. Not sure why version 1.6.0 doesn't show up in the list of available versions in the nuget gallery but is still available.
is working on a reply...