Hello all,
we have just made our first test-Migration from NAV 2013 R2 to NAV 2016 for one of our customers. The Migration went well (with one or two small bumps on the way) but now we have a bigger problem.
The customer used the approval module quite a bit in the old database, which is now the new workflow module. In the Cronus company you have the workflow templates with the defined Steps and can create new Workflows from these. But after our test-migration the already from NAV 2013 R2 existing companies have no (or very few) workflow steps and the templates only exist without assigned steps. Importing workflows from a 2016 Cronus isn't helping due to the missing steps. You also can't export and import the templates, as the standard programming in the workflow tables does not allow you to create your own template data.
Does anyone know why this is? Did we do something wrong during the upgrade? Or is this something that Microsoft forgot to integrate into the upgrade process?
Thanks for any help in advance.
Ciao,
Lils
0
Comments
Its there and the Templates comes by Default. Even if you customer is using standard Approval Process the Upgrade Routine Enables the Workflow for the Required Approvals.
You can check / answer following questions =
1. Did you forced objects when you imported NAV 2016 Objects in database?
2. Try Initializing Company Using Codeunit 2. (By Default this is part of upgrade routine and it have everything that enables workflow templates).
Reference - Codeunit 2 (Run Trigger) - WorkflowSetup.InitWorkflow;
3. If your customer is using approvals, then check are there any contents in approval entry and posted approval entry tables.(454 & 456).
** Point 3 will also confirm about point 1.
Only missing part from Microsoft as a part of upgrade Routine is they are not deleting the Un-used objects.
Do let me know your findings.
Thanks & Regards,
Saurav Dhyani
Do you Know this About NAV?
Connect - Twitter | Facebook | Google + | YouTube
Follow - Blog | Facebook Page | Google + Page