You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It makes sense to me that flow mapping would not work within a library as they are intended to be static. However, I found that when I tried to flow map in a database that contains a library, ALL of the exchange values were being deleted from library processes that contained one or more of the mapped flows. Flow mapping still works within foreground processes, but is dangerous if library processes are being edited in this way.
When I discovered this issue I was mapping elementary flows using a csv based mapping file. I have not confirmed the effect when using a JSON-LD mapping file.
The text was updated successfully, but these errors were encountered:
It makes sense to me that flow mapping would not work within a library as they are intended to be static. However, I found that when I tried to flow map in a database that contains a library, ALL of the exchange values were being deleted from library processes that contained one or more of the mapped flows. Flow mapping still works within foreground processes, but is dangerous if library processes are being edited in this way.
When I discovered this issue I was mapping elementary flows using a csv based mapping file. I have not confirmed the effect when using a JSON-LD mapping file.
The text was updated successfully, but these errors were encountered: