Duplicate Configuration Folders

Unknown

Duplicate Configuration Folders

Unknown

We are running into an odd problem in our production environment. So a little bit of background on the issue, to help solve an issue we were facing in DEV, we created a new Data Config folder for one of our Folder Execution Extension structures and deleted the older one in hopes the issues would go away. Eventually, we did resolve all problems in DEV, however, when we went to import the new code to production we saw that because the Config & Data folders had different folder IDs now, the production environment created two new folders (see below) for our Config & Data folders.

These new folders are MyType Configuration(0) & Data(0) and they are storing the newly created entities as well as the migrated flows that were in the Config folder. Because the folders marked with (0) contain the new code all of our older data is using the new code and the older data is using the old flows still.

My question is, how can we safely combine these two folders without compromising any existing entities?

[img]att1[/img]

Unknown

Hi,

By making a copy of everything in your project including your flow execution extension, mapping the copied type into the copied and updated flows, and importing it all as a new project in your production server, you have ended up with two distinct projects using separate data types. You can confirm this by checking the namespace of both flow execution extension types. Though one was made by copying the original, they are still treated as completely different types. To rectify this situation, you would need to either:
[ul][li]Update the old project with the same changes implemented in the new project[/li][li]Create a flow that will ingest every one of the old flow execution extensions and convert them to the new type[/li][/ul]
Here is an example project that shows how to do this. Due to the nature of projects, this will not work for your project, but you can use it as inspiration to create something similar for your data.