Sign up to take part
Registered users can ask their own questions, contribute to discussions, and be part of the Community!
Registered users can ask their own questions, contribute to discussions, and be part of the Community!
Hi,
I have a flow-zone with name A. In there, I renamed a recipe and now it appears in flow-zone Default. There is no way to move it back to flow-zone A.
Does anybody have an idea?
Saul
Hi @saulleon,
I have run into this issue as well. That is, that renaming a recipe in a flow zone moves it back to the default zone. Hopefully this will get fixed in a future release of DSS.
In the meantime, I believe what I have done is move the downstream dataset from the other flow zone (in your case A) back to the default flow zone. Then move that downstream dataset back to A. That will bring the renamed recipe with it. It seems that only datasets can be moved to a flow zone (recipes can't be moved directly) thus the need to move the associated dataset to get the recipe moved.
Hope this is helpful.
Marlan
Hi @saulleon
You can use integrated version control to revert renaming. For this please navigate to Version control
find the commit where you have renamed the recipe and click on commit ID:
revert the change:
Please note that you will revert all the changes to this point.
Thank you Sergeyd,
I don't want to lose changes, so this solutions is not for me.
Hi @saulleon,
I have run into this issue as well. That is, that renaming a recipe in a flow zone moves it back to the default zone. Hopefully this will get fixed in a future release of DSS.
In the meantime, I believe what I have done is move the downstream dataset from the other flow zone (in your case A) back to the default flow zone. Then move that downstream dataset back to A. That will bring the renamed recipe with it. It seems that only datasets can be moved to a flow zone (recipes can't be moved directly) thus the need to move the associated dataset to get the recipe moved.
Hope this is helpful.
Marlan
Hi @Marlan
Yes, it's scheduled to be fixed in the upcoming releases.
Thanks Marlan! This did the trick!
Hopefully we can have this glitch fixed in future versions.