Recreating Recipes

When you instruct Dynamics NAV to transfer production BOMs to Genesis R&D, the default behavior is for ESHAPort to only create new recipes in Genesis. If you export a production BOM from Dynamics NAV for which a recipe already exists in Genesis, ESHAPort will skip it when it is importing data. Using this type of configuration, any changes that are made to production BOMs in Dynamics NAV for which a corresponding Genesis recipe already exists will not be imported into Genesis during a data transfer.

If you want to update an existing Genesis recipe to reflect changes that have been made in Dynamics NAV, you can place a check mark in the Recreate Recipes field on the Genesis Integration window prior to exporting data. When you instruct the system to transfer recipe data for a production BOM that currently has a corresponding recipe in Genesis, it will replace, rather than ignore, the existing Genesis recipe. The current Genesis recipe is deleted, and a new recipe is created in the database.

When a Genesis recipe is deleted during the recreate process, any additional information, such as nutritional overrides, that is associated with that recipe will be deleted as well. Be certain you have set the proper filters for the BOMs you wish to export before you recreate recipes.