-
-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Date field in import-export entity content with different formats #3487
Comments
It's confirmed. |
I don't fully understand the issue. The [] placeholder is kind of a "null" placeholder. Is this causing the problem? Are you saying that the rows with the [] in the date field are causing problems? Just on that field, or the entire row? What is the result? |
Could be. But the issue is in the format of the last two rows. |
ok, got it. thanks @enfJoao for clarifying |
could you also include the xml snippet in this issue, so we can better see what's really there? |
But I did take a look at it and it seems the dates share the same format. The [] null values in the second column (end date) makes excel treat the filled values as text instead of dates, apparently. So 2sxc fails to import those (with no error whatsoever). Any way to improve excel management of these dates? A better app for xml editing perhaps? I do need this monthly. |
So it appears that both columns use the same formatting. Do things only break, if you've edited them in Excel? So is Excel changing something if you open/save? Or is a simple reimport (without editing) also breaking? |
Thanks. |
There have been many issues in the past where the recommended solution was export - change - import. Change a data type is one of them. If changing data in excel is not reliable, then you can recommend a better xml editor that works with 2sxc readable data formats. |
I'm submitting a
[x] bug report
[x] not sure
...about
[x] Content Types or data management
[x] other / unknown
Current Behavior / Expected Behavior
I have an entity that I export-import monthly.
It contains two date fields. One always imports, one always fails import (the second one only requires minimal manual fix within 2sxc for a couple items).
Today I exported the entity again to xml and saw a potential issue:
The entities are exported with a different format (and probably expects a different format on import too, so it fails).
The configuration is exactly the same for both.
I manage the xml in excel, if it matters.
Your environment
The text was updated successfully, but these errors were encountered: