Subqueries in EG ... is there any construct for local templates?

[fja]

Hello!

I am struggeling with task templates in EG. I would like to use them to build up subqueries. 

A subquery is normally imited to a project, i.e. does only make sense in that context ... now as I do not want to litter the place with "use once" templates for specific (sub)queries:  Is it possible to limit templates to project scope .. or is there something like a temporary tempate?

Cheers

FJa

[Kurt_Bremser]

Please define what you mean by "template". In a SAS context, I associate "template" with ODS and PROC TEMPLATE.

[fja]

Hello Kurt!
Thank you for your reply. In EG you can store an sql query (generated by EG) as a task template. These can be used to build up subqueries in an point and click fashion. I am not sure if they are in line with the term template in the PROC TEMPLATE context.
Cheers

edit:

.. and i did not manage to find them using list with PROC TEMPLATE ... but they get listed in the template section of tasks in the EG UI ... so my answer to your question would be a careful 'no'. But I am on shaky ground here.

[AhmedAl_Attar]

Hi @fja 

Here are couple of resources for you to look at

• Finding Your Inner Query with SAS® Enterprise Guide
• SAS Enterprise Guide: Hidden Gems

Hope this helps

[fja]

Hello Ahmed!

Thank you very much for your contribution. I do know the first link. It is a fine Introduction to the usage af task templates ... but does not answer the question posed, unfortuately.

The scond link is new to me, I will have a look during lunch ... and will report 😉

Cheers fja

edit:

The Webinar quoted is full of nice tips but does not answer my question (posed in the intial posting).

[Kurt_Bremser]

I see. I am quite some time away now from EG (having retired last year), so I have come back to being a pure "code programmer".

And I have almost never used the Query Builder back then, I have found that I am usually faster typing my SQL code than using the point-and-click interface.

So my approach would rather be to pack often used code snippets into autocall macros.

[fja]

Hi Kurt!

Congrats to your ritrement! 😃 ... I have read about that on LinkedIn.

You are all correct that typing SQL directly is way faster and provides way more control. It is just, that I am currently working for "business users" ... hence the question.

Cheers fja