Hi @MikeLR
"Simple" is very broad word and shouldn't be the only criteria to use to determine if a workflow is good or even great(@clmc9601 might want to chime in here) . Does it produce the correct output? Does it scale nicely(if required)? Is it easy to maintain? Does it handle errors gracefully?
The workflow as it stands appears to be as simple as it should be. The output is correct. Scaling won't be an issue since it's unlikely that we'll have millions of currencies. Every step is well documented and each performs a specific task. Someone looking at it once you become the CEO of your company, will have no problem determining how it works.
The only place where you could add some complexity is around error checking. What if the layout of the webpage changes or the site is unavailable?
Technically, you could replace the ahref regex tools with a single formula tool with either Regex_Replace() or case-insensitive Replace() functions. This would reduce your tool count, and if you use Replace() it will run faster than the equivalent Regex_Replace functions. However, since you only have ~200 rows in your dataset, there won't be an appreciable increase in speed.
It's probably possible to amalgamate most of the regex operations into a single expression, but this would increase the overall complexity of the regex, while reducing maintainability.
To sum up, this is a good workflow. Some error handling would turn it into a great one.
Dan
