How to inspect a services dependencies

It can be helpful to verify which bridge models, attributes, categories, trees, routines, and handlers a service uses before creating the package to move that service between environments. This can give another way to check if a new attribute, category, routine, etc will need to be moved as well.

This can all be accomplished manually and via the API. This service leverages the API to create a list of these elements that are related to any service in the space into which it is loaded. Each element listed is a link that will create a file you can download to aid in building a package for that service.


These export files can be imported via the API or, in the cases of forms, trees, routines, and handlers, through the import interfaces for those items.

Did this page help you?