Flow breaks after import

Unknown

Flow breaks after import

Unknown

Hi,

We are having some issues deploying our project to a UAT/Prod server. We export the project with dependencies, and on DEV we have no errors within a certain flow. When we deploy our project out it has an error that makes the flow not work correctly. We have exported the project out several times and have deployed it to two different servers with no luck. Just looking to see what is wrong here and maybe we are exporting our project incorrectly (Although we have done this deployment the same way 4 different times in the past with no issues). Were getting a type mismatch error in a subflow named Get Unique Strings from List. Again this does not produce any errors on our development server, but after importing the project to production, the error occurs. Please contact me as our deployment has been missed here because of it. The good thing is that we were able to roll back our deployment to the previous version. Thank you very much!

Unknown

Did you modify Get Unique Strings from List from its original configuration?

Get Unique Strings from List is a [b]system default[/b] converter flow, and if you alter its inputs or outputs and use it in your project, youre going to run into some issues. Because it is a system flow, when you reference it in a project, it will only be referenced by its [b]Flow ID[/b]. A copy of this flow lives in every installation of Decisions and every single one of them has the same [b]Flow ID[/b]. So when you import your project with a reference to an altered system flow and try to run it, youll get an error.

[b]Since you changed the inputs to Get Unique Strings from List, the flow calling it is trying to send a list of a custom type into Get Unique Strings from List because its configured to do that - but the local version on the UAT/Prod server of Get Unique Strings from List accepts a list of strings - and that results in a type mismatch.[/b]

To avoid this error and ones like it in the future, go back on your dev server and [b]restore Get Unique Strings from List to its original configuration[/b]. Then [b]make a copy of it[/b], [b]make the desired changes[/b] to it, and [b]include the newly copied version of the flow as a part of your project[/b] instead of an internal Decisions project. Alternatively, you can modify the version on UAT/Prod as well, but that is a bandaid solution and may break any other flows calling Get Unique String from List.

Every time you want to change a System Designer Item, make a checkpoint, then make a copy, make your changes to the copy, and include the copy in a project.
[i]edited by james.hartzell@decisions.com on 2/6/2020[/i]