Emerson Exchange 365

• Not Answered

Recipe backwards compatibility (from v13.3.1 to v.113.1)

Hi,

Is there a "gotcha" to consider when importing a recipe FHX file into v11.3.1 that was exported from v13.3.1?

System background:  Our PROD environment was recently upgraded to v13.3.1 from v11.3.1.  We also a SIM environment that currently runs v11.3.1.  The DB in the SIM is the same as the DB in the PROD pre-upgrade.  I was wondering if exporting a recipe from the v13.3.1 PROD system would work if I import it to the v11.3.1 SIM system.

Looking forward to seeing some feedback and guidance if this is possible and are there work-arounds if not.

Regards,

ccd93362

ccd93362

• 21 Mar 2018 6:13 PM
• Cancel

1 Reply

• Andre Dicaire

  

  • 21 Mar 2018 6:42 PM

  In most cases, if you have not configured any new functionality from the new version, the FHX will import into the older version. You have to strip of the version header information, as this will prevent the import from starting.
  
  You definitely want to select No To All and not import any default database objects. And I would make a back up of the database prior to the import.
  
  You can also take an export of the v11.3.1 recipe and its migrated version in 13.3.1 and compare them for differences. this will show you any structural differences the migration may have created.
  
  The FHX files typically only include data that is different from default information. So even if there are new features in the later version, as long as you haven't modified their default settings, the FHX will not contain those parameters, and the older database imports the FHX. As soon as the new feature is configured, the FHX may no longer import in the older database. Then the fun begins.
  
  Note there is no support for backward FHX imports. Emerson does it's best not to modify FHX content, but ultimately, the goal is to support forward migration. The FHX importExportprogress log will record any issues and you would then have to "correct" the FHX to import.
  
  There are three new Function blocks in v13 that will break import to v11.3, once you actually use them in a module. I'm not aware of any recipe changes, but not all changes are necessarily documented. If new fields have been added to objects and these are in the FHX coming out of v13, you'll have to identify and remove them in order to import.
  
  Note that even if you compare the v11 and v13 FHX content, the differences may still import. One such change was made during import of the FHX to address duplicate references to Embedded blocks. The database now prevents this situation from happening, but in v11 and earlier, one could end up with multiple modules referencing the same Embedded block, which is intended to be a uniquely referenced item. During import, the duplicate references are identified and the affected Embedded block is copied and unique references created. Upon import to v11, this new FHX from v13 would still import, but would be different if compared to the original v11 export.
  
  So you'll have to be vigilant and understand any differences, and as long as you can take ownership of any "Issues" this creates, you'll probably be able to do the import.

  Andre Dicaire

  • Cancel