Upgrading existing Hydrator Pipeline export files to the new release is difficult and time consuming
Description
Release Notes
None
duplicates
Activity
Show:
Dave Finnegan September 6, 2016 at 10:38 PM
The 3.4.x export files will not load or render. The issue is with the version numbers. Although, with other releases there have been syntax changes in the configs, as well.
Albert Shau September 6, 2016 at 8:55 PM
Can you give some more detail on the behavior you were seeing? Does the UI reject files from 3.4.x? Or does it accept them but not render them correctly?
There weren't any changes made to the config from a backend perspective, and there is also an upgrade tool that people can run. But the UI also stores some extra stuff in the config so if there were backwards incompatible changes, that would explain problems.
Duplicate
Pinned fields
Click on the next to a field label to start pinning.
Created July 26, 2016 at 6:01 PM
Updated September 14, 2017 at 11:41 PM
Resolved September 14, 2017 at 11:41 PM
Updating existing Hydrator pipeline export files (e.g. from 3.4.3) for use in 3.5.0 is very difficult and time consuming.
There are many changes to the export file syntax requiring that most pipelines be recreated by hand, in part, or in whole, in order to get them to work in 3.5.
It should be possible to load a 3.4.3 version export file and have the UI prompt to auto-upgrade the pipeline definition on import.