I have often found myself rewriting the same command line scripts to parse through the Planning Analytics data directory.  Here are a few common use cases for doing so:

1) Checking dependencies of objects

a. Ex. Without opening all the chores, how can I confirm which chore runs the process “Cube – Finance – Load Monthly Data from File”?

2) Remove unused Planning Analytics objects

a. Ex.  There are several processes that have not been run within the last 6 months. Before deleting it, how can I quickly confirm that it is not called by any other process?

3) Outputting a list of all the objects in a migration package

a. Ex. I would like to document a migration and would prefer not to manually type the names of the objects into an excel file or word document.

There are likely other scenarios where it would be helpful to “search” the Planning Analytics data directory. Rather than rewriting the same command line scripts, it is possible to save a Windows Command Script and include a prompt for a search string.

Here is a screenshot of the Windows Command Script. In this instance, the search directory is set to be the folder named “Data”.

The Windows Command Script must be saved at the same level as the “Data” folder, or the folder specified in the searchdir variable.

You can then launch the “SearchTM1Objects.cmd” script where you will be prompted for a search string:

Type in the search string and hit enter.

This will generate a text file that displays all the objects that contain the string “Cube – Finance” in the data directory and will display the objects based on their type, whether it be a Rule, TI Process, or Chore.  Now we can quickly see that the “Cube – Finance – Load Monthly Data from File” process is called by the chore “Daily – Finance Data Load 5AM EST”. Let us know if you have other use cases for this type of functionality!