2 Replies Latest reply: May 15, 2014 9:57 AM by sienayr _ RSS

    Dynamic export file names with filters

    sienayr _

      Monarch v8.01


      I have a model that applies to identical reports layout wise, but have different versions/report numbers.  I only want to maintain one model for all of the different reports.  Therefore, I need to be able to specify the file output name dynamically, so I know which report the output file came from.  I use command lines for automation.


      I have six different filters that have to run and produce separate output files each time a report is processed.  My problem is that with /exp, I have not found a way to specify a filter.  If I could, I would use /exp six times, specifying a different filter each time with a unique output file name.  It sure would be nice if there was a filter switch that would enable this.


      With /px, the path and file name have to be pre-defined, so I am unable to tell which report a file came from, and the output files would either be overwritten or appended to every time a different version of the report comes through.  I need each of the six output files to be unique every time a report is processed.


      When I use the /exp switch, is there a way to specify that a certain filter be used when exporting the file?


      Alternatively, is there a way to specify a pre-defined project export (/px), but specify a different file path at run-time, or somehow change or override the specified path?


      Any other ideas on how this can be accomplished?


      My only other option is to have duplicate model files for every version of the report, which I really want to avoid.


      I looked around on the forum but didn't see anything like this, if I missed a relevant post, please point me in the right direction.


      Thanks for any help!



      [size="1"][ August 02, 2007, 06:29 PM: Message edited by: sienayr ][/size]

        • Dynamic export file names with filters
          Grant Perkins

          Hi RN and welcome to the forum.


          Some interesting challenges there and a lot to consider  - more than I have time to work through right now but I anticipate others with similar requirements who already have solutions may be along soon.


          My first reaction was to point you in the direction of Data Pump since you seem to have some volume of work here (assuming ths is not a once a year process ....) and Data Pump might just prove cost effective and give you all the controls you need.


          My second thought was that if you use project exports you should (I think) be able to set up separate export jobs for each filter within the overall project export and then just run the project ( A very top level description which you have probably already investigated and found wanting but my reading of your description of the problem seemed to me to leave the question open ...). Or use multiple /px enties in the line to specify which jobs contained in the project you actually want to run. Or multiple lines, one per job, and then specify where they are to be sent, overriding the default if necessary.


          My third thought moves on to your multiple model idea to observe that with Monarch V9 Pro you could develop one model as the master and then create and use other models Strongly Linked to that master model with substitutions for the bits that set different parameters. That way of the core model needs to change you change the master and the others will follow but retain their substitutions unless something breaks them. The linked models can be protect from changes other than via the master model.


          I guess a fourth option would be to script something based on the input file name to change the name of the output once the export has finished - a stage in the process that would be external to Monarch.


          As I mentioned back at the top I may have missed something here and it is a while since I have had to grapple with this sort of requirement  - others are likely to be more recently experienced!






          • Dynamic export file names with filters
            sienayr _

            Thank you for your reply, my solution is to dynamically create a project file every time for every version of the report, inserting the output file paths and current report path into the XML parameters as needed.  It is working great, and provides a lot of flexibility.


            Thanks again,