Skip to main content
Solved

find out, in which workspaces a certain deployment parameter is being used


vki
Contributor
Forum|alt.badge.img+7
  • Contributor

Hello

I have to change the value of a deployment parameter. Is there a way to find out, in which other workspaces this deployment parameters is being used?

Thanks, Vera

Best answer by virtualcitymatt

You can get the dependencies of a workspace using the v4 rest API. The call is:

$(FME_HOST)/fmeapiv4/dependencies?id=@Value(repository)/@Value(name)&type=workspace

For this to work you need to fetch all of your workspaces, thankfully there is already a CustomTransformer in the hub which will do this. 
 


This obviously only applies to workspaces which are published on FME Flow.

Let us know if you also need to get that kind of info out of a workspace file itself

(Note this can also be used to look for dependencies of Web and Database connections too). 

View original
Did this help you find an answer to your question?

3 replies

virtualcitymatt
Celebrity
Forum|alt.badge.img+36

You can get the dependencies of a workspace using the v4 rest API. The call is:

$(FME_HOST)/fmeapiv4/dependencies?id=@Value(repository)/@Value(name)&type=workspace

For this to work you need to fetch all of your workspaces, thankfully there is already a CustomTransformer in the hub which will do this. 
 


This obviously only applies to workspaces which are published on FME Flow.

Let us know if you also need to get that kind of info out of a workspace file itself

(Note this can also be used to look for dependencies of Web and Database connections too). 


vki
Contributor
Forum|alt.badge.img+7
  • Author
  • Contributor
  • June 10, 2025

Great! Thanks a lot!

You are using the API V4 here. According to the documentation it’s still under active development and it’s not recommended to use it in production environments.

But for my purpose, to get this list of deployment parameters, it obviously works very well.

Thanks, Vera


virtualcitymatt
Celebrity
Forum|alt.badge.img+36

Yeah but I think it's pretty stable now - the FME Flow UI is built on it and I think it's unlikely to change substantially. Most likely it's better to build anything against this v4 APi vs v3 which is likely to get deprecated soon.


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