Pretty much every dataset I produce has some common columns, these contain the Sector, Region and Office that the line of data is linked to. Data is often distributed to a Sector, a Region or an Office and usually this is done by dumping the entire dataset to an Excel spreadsheet and using slicers etc to allow individuals to make their own decisions about which data cut they want. This is all fairly new as a way of working and I'd like to improve things because often having a full data-cut causes security concerns or simply means there's too much data for antiquated machines to run comfortably. I'd like to add a Code Node to my Enterprise Guide process flows that creates multiple tables, one for each <parameter> and filters each table by that parameter. The parameters would be the Sector, the Region or the Office, so for example if I wanted to use the Region, I would end up with 8 output tables, one for each Region. If I could do that, that woujld be amazing. But if it's relatively simple, I'd like to be able to use multiple parameters, as some times it would be very useful to break the data down further, for example a Region's data broken down by Sector. In most cases I would want to export the results to Excel, I don't have access to any of the services around that other than right-click, 'export results as a step in the process'. So a code that incorporated the export would be really helpful too. Obviously I'd need to specify a location in the Code Node and the export needs to be .csv as the way Enterpise Guide builds .xls files (the referencing between the different .xml files is either relative or the opposite I can't remember which) means they can't be used as Data Connections in Excel. Data Connections are really useful for us as they allow us to build process flows that automatically update the Excel-based products that we deliver. Hope that all makes sense, but if any part isn't clear, just let me know. Thanks in advance!
... View more