Hi Chris
When I first read your answer I thought you're talking about some wizard generated loop construct.
I would have bet that my proposition works (just pack the whole flow in a macro and then execute the macro).
So I tried now with a very simple example - and yes, you're right, it didn't work when I ran the whole branch (EG 4.3).
That actually confused me quite a bit so I exported the whole branch and copied it into a single code node. And then I executed this code node and it worked. Hmmm...!!
Honestly, Chris! If you want EG to be a developer’s tool then you will have to have a developer mode added which basically means:
- Add NOTHING to the code written
- WYSIWYG in regards of code
I have currently to use EG for writing ETL processes which in the end are executed in batch.
The only thing which I prefer over using good old PC SAS is that I just can disconnect/reconnect if my code goes berserk and that it’s very easy to execute the same code in different environments/on different servers.
But besides of very basic unit testing EG is more of a hassle than a help.
I sure can’t use any of the wizards because as we know if I later on would like to export the code I will get heaps of EG “garbage” which might even not work in batch unless I tweak the config.
And now I even learn that an exported flow executed via EG doesn’t behave the same as the flow executed directly in EG. I think no further comment is needed here.
Sorry Chris for my tone. I’m just a bit frustrated in the moment.
I appreciate your commitment and contributions to make the SAS world a better place a lot.
Thanks
Patrick
Message was edited by: Patrick