Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
I Import and Export Application
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • External wiki
    • External wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Sigsiu.NET GmbH
  • Import and Export Application
  • Issues
  • #13

Closed
Open
Created Mar 15, 2018 by Sławek Sikora@SikorReporter

Calendar field structural data format for simple date

Using full structural data for importing calendar field simple date return 500 internal server error in the console and import process hangs. Basically it wouldn't be a problem as long as it wouldn't be a method which use imex for export. In the moment when someone want to export this data and then import it back in other place, he need to edit all records to maintain correct format.
For summary, these two methods works for import:
"1504093541"

"{
  ""timestamp"":""1504093541""
}"

This generate server error:
``` "{ ""string"":""31.12.2017"", ""timezone"":{ ""offset"":0, ""timezone"":""UTC"" }, ""struct"":""1514732687.847"", ""timestamp"":""1514732687.847"" }" ```
I think it also didn't work in the Imex 2.2, but would be good at least to not break import process but at skip this data and left field empty.
Assignee
Assign to
2.3
Milestone
2.3 (Past due)
Assign milestone
Time tracking

footer

Legal Notice / Impressum | Data Protection / Datenschutzinformation