Skip to main content
Open

Copy/move workspaces to other repository

Related products:FME Flow

revesz
Contributor

When it is about to move or copy a workspace to another repository (from test repo to live/scheduled, making it available to other teams, etc) the way to do is to download and publish to the other repository taking care of the data upload and service settings.

It would be much more convenient if a workspace could be copied in the web interface with uploaded data, services and notification settings.

7 replies

Forum|alt.badge.img
  • April 30, 2019

I would be very interested in such a functionality. Most of our development cycles have milestones that require code to be frozen. We are finding it tedious to check in 75+ workspaces to a new repository after each milestone.

 


jdh
Contributor
Forum|alt.badge.img+28
  • Contributor
  • May 1, 2019

@arunm Could you use projects for your requirement?


Forum|alt.badge.img+3
  • June 4, 2019

We have the same issue. FME Server managers might be a different person then the original publisher. Sometimes the FME manager would like to move workspaces in different repositories so they can be assigned to different queues. For example devide the slow workspaces from the fast one. Now we need to load into FME desktop, publish into another Repository and remove the old one. A move option on the web could reduce the burden and provide more control to the server manager.


panda
Enthusiast
Forum|alt.badge.img+17
  • Enthusiast
  • February 18, 2022

Been awhile since this post, but this functionality would help manage FME Server Repository easier for sure!

 


LizAtSafe
Safer
Forum|alt.badge.img+15
  • Safer
  • February 8, 2024
The following idea has been merged into this idea:
All the votes have been transferred into this idea.

LizAtSafe
Safer
Forum|alt.badge.img+15
  • Safer
  • February 8, 2024
The following idea has been merged into this idea:
All the votes have been transferred into this idea.

LizAtSafe
Safer
Forum|alt.badge.img+15
  • Safer
  • April 5, 2025
The following idea has been merged into this idea:

All the votes have been transferred into this idea.

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings