Hey there,
We are setting up a process, and it would be nice to be able to pull the monthly econ results from specific Eco Runs.
The only deferrable filter I see on the “get eco runs” route is to filter by “tags”, but our engineering team is having trouble finding where exactly and how they are able to add such tags to a eco run?
Any suggestions / guidance on where to input tags on eco runs?
Hi Adam, sorry for the delayed reply here.
We likewise see the “tag” for econ runs that you mention in the question, but unfortunately it seems that tagging econ runs has been an unsupported feature for quite some time.
Regardless of that, we want to support your process in getting monthly results from econ runs. We currently recommend utilizing project ID’s and scenario ID’s to fetch econ run ID’s due to its specificity and uniqueness. If there is a concern with this filtering method, please feel free to reach out and we can work out something to make your lives easier.
Hey there,
That is unfortunate to hear.
I am going to explain a bit about what my team is trying to do, I am strictly software, so apologies in advance if anything I say about the CC platform is incorrect, I only open the front end to check things sometimes.
The issue with the method that is currently available, is that it doesn’t really allow for dynamically grabbing the eco run we want, I.E I can have multiple eco runs with a project - scenario combination, but I am only looking for 1, I then want to use the econ run id to generate a monthly export.
With the “get eco runs” route having no true categories for the engineers to input on the front end, I basically have no way of grabbing only the correct eco run id.
I.E to complete what we want to do, we would need to come up with a manual process like “don’t run this automation until you run the eco run you want used in the analysis” then I just grab the latest run eco run id.
this would all be solved if there could just be a name attached to an eco run, then I can filter by name to grab the correct eco run from the return of “get eco runs” and proceed with the needed workflow.
Usually for a project - scenario combination, there should only be one econ run per that combination. Only thing I can think of that might ruin that uniqueness is if multiple users have ran a run on that scenario.
Hmm, yeah whenever I run this route for the project - scenario combo we want to grab from, I get back multiple eco runs.
If I’m not mistaken, the engineers say they can run multiple eco-runs for a given scenario and change out different qualifiers and combos, we want to grab the eco run with the specific combo + qualifiers that have been applied, not just any run that happens on that scenario, so I don’t see how I would be able to determine that without marking the specific eco run in some way.
They are able to have multiple econ runs but fetching-wise it’s hard to grab anything but the latest run for each user on our side, due to some overriding that happens after a new run is ran for a user.
Regarding the feedback on tagging econ runs, we can implement a feature to distinguish econ runs for the API calls better. Is tagging something you’d prefer being done through the API or through some UI on the website?
I see, so yeah like in our case, we would have to make it know that before you run this automation, you need to do an eco run, and we would grab it like that, which of course that would work, just not preferable / probably wouldn’t want to try and implement a system to go based on that.
I would think having the ability to tag the eco-run on the UI, and just being able to filter by the tag on the api side would do the trick, that’s what I was planning to do initially, as it looks like the current api docs hadn’t been updated to remove the tags that use to be on the eco-runs.
We can implement something like tagging feature for our econ runs, but this won’t eliminate the need to run econ runs, since in order to tag the run they’ll need to run econ again.
A potential workflow could look like this. Client opens up the econ run dialog → inputs desired tags → runs econ → engineers on the software side can fetch said econ run using those tags.
What we don’t have the functionality for is automating the first three steps, and probably won’t be able to add those in the near future.
Gotcha, completely understand, for now I think we are just going to avoid this, and go down an alternative route and see if we can’t get a similar result for what we need.
Thank you for responding!
Just to clarify, would still love for this to be implemented, I think our engineering team has a lot more they want to be able to do with this, and tagging would definitely make things easier, I understand it won’t be a near item on the roadmap, but would be nice to have at some point.
We’ve added this to our client feedback product board, and although it is down the line, we don’t have a lot of requests on the API side so it shouldn’t be too long of a wait.