Sincere apologies for getting back so late! However, this issue does still exist in our Azure environment.
We generate an Exporter syncpack in our local IIS dev environment and upload to our Azure Environment. Looking at the details of one of the date nodes, everything looks normal:
However, after import, the date month and day are reversed (left is local dev, right is Azure)
And we get some dates that are invalid after the reversal and which cannot be displayed so we cannot publish the node:
If I try to import the same syncpack again, this is what happens
After import we still end up with invalid dates. Obviously, with invalid dates we cannot publish the node so we have to manually adjust.
Hopefully that's enough info. Let me know if you need more.
Guessing a little, but i think the azure site is miss parsing some of the date values from the file.
on the import we take a sortable date (e.g 2024-08-26 ) and convert it to a date - my guess is the default parse isn't working for the sites culture on azure .
We have an updated version that now does a specific parse for the sortable date and falls back to the other one. I am hoping that fixes this.
but we are about to take a week break here, so We are not going to be in a position to release this as a Umbraco release for at least 10 days - and even then, it will take a little while as we have to version test for other versions etc.
(the v8 release above has no other differences from v8.11.7 than this commit.https://github.com/KevinJump/uSync/commit/1adb4b56fe28b5eaafd4861947fdb9eac23f6e87 so it should be a fairly stable version for testing)
Running Exporter syncpack on Azure appservice imports invalid date format
Hi Kevin
Umbraco 8.18.7
uSync Complete 8.11.13
uSync - 8.11.7
I originally posted about this issue some time ago in https://our.umbraco.com/packages/developer-tools/usync/usynccomplete/111470-usync-exporter-potential-issue-with-date-picker.
Sincere apologies for getting back so late! However, this issue does still exist in our Azure environment.
We generate an Exporter syncpack in our local IIS dev environment and upload to our Azure Environment. Looking at the details of one of the date nodes, everything looks normal:
However, after import, the date month and day are reversed (left is local dev, right is Azure)
And we get some dates that are invalid after the reversal and which cannot be displayed so we cannot publish the node:
If I try to import the same syncpack again, this is what happens
After import we still end up with invalid dates. Obviously, with invalid dates we cannot publish the node so we have to manually adjust.
Hopefully that's enough info. Let me know if you need more.
Cheers
Jules
Hi Jules,
Guessing a little, but i think the azure site is miss parsing some of the date values from the file.
on the import we take a sortable date (e.g 2024-08-26 ) and convert it to a date - my guess is the default parse isn't working for the sites culture on azure .
We have an updated version that now does a specific parse for the sortable date and falls back to the other one. I am hoping that fixes this.
We have a nightly release to test this: https://dev.azure.com/jumoo/Public/_artifacts/feed/nightly/NuGet/uSync.ContentEdition/overview/8.11.8-build.20231012.2
but we are about to take a week break here, so We are not going to be in a position to release this as a Umbraco release for at least 10 days - and even then, it will take a little while as we have to version test for other versions etc.
(the v8 release above has no other differences from v8.11.7 than this commit.https://github.com/KevinJump/uSync/commit/1adb4b56fe28b5eaafd4861947fdb9eac23f6e87 so it should be a fairly stable version for testing)
HI Kevin
Thanks for the quick response!
I can add the nightly and downgrade if issues.
Hopefully it will fix.
Have a great week off!
Jules
Hi Kevin
Still seeing same issue I'm afraid
Jules
This issue fixed in
https://our.umbraco.com/packages/developer-tools/usync/usynccomplete/112989-usync-exporter-date-issues-persist
is working on a reply...