When running USync a lot of the dictionary nodes are created as unparented when they instead should be created as a child of another dictionary node.
This is how it should look like:
But after the import it looks like this:
E.g. "Anchor" should be a child of the "Backoffice" node and "Anchor.Anchor name" should be a child of "Anchor". I can see in the config files that they point to the correct parents, e.g. for the "Anchor" it looks like this:
<Parent>Backoffice</Parent>
But this is not reflected in the hierarchy. Anybody know what went wrong?
Great, thanks! We actually tried a second import, but due to the OneWay option being enabled it didn't work. But after disabling this the hierarchy is now correct. Thanks again.
USync not importing dictionary nodes in correct hierarchy
When running USync a lot of the dictionary nodes are created as unparented when they instead should be created as a child of another dictionary node.
This is how it should look like:
But after the import it looks like this:
E.g. "Anchor" should be a child of the "Backoffice" node and "Anchor.Anchor name" should be a child of "Anchor". I can see in the config files that they point to the correct parents, e.g. for the "Anchor" it looks like this:
But this is not reflected in the hierarchy. Anybody know what went wrong?
Hi Claus,
what version of uSync / umbraco are you running?
Kevin
Hi Kevin
We're using uSync.ContentEdition 8.5.0.1 and Umbraco 8.5.4
Hi Claus,
yes, it looks like we have an issue where we don't check the level of items before import.
For now : a second import fixes the order, and we have a fix ready for the next release.
https://github.com/KevinJump/uSync8/issues/85
Hi Kevin
Great, thanks! We actually tried a second import, but due to the OneWay option being enabled it didn't work. But after disabling this the hierarchy is now correct. Thanks again.
Claus
is working on a reply...