Limiting glossary in report to definitions and parameters

[Richard Burke]

Hello,

We are using the EA report generator in 12.1 to generate custom reports. Our glossary has a lot of terms so we want to restrict it to definitions and parameters.

I was hoping to use the filters built into the report generator but I couldn't find anything that looked like it did the job so I resorted to custom SQL.

I created  a fragment with the following (MySQL) SQL:

Code: [Select]

Select
  t_glossary.Term As Term,
  t_glossary.Type As Type,
  t_glossary.Meaning As "Meaning.Formatted"
From
  t_glossary
Where
  (t_glossary.Type = "Parameter") Or
  (t_glossary.Type = "Definition")
Order By
  Term
The Meaning.Formatted is so that formatting is maintained when the glossary is printed. Otherwise you get <b> </b> instead of bold text, for example.

When I run the report, I get the following error message:

Code: [Select]

Error:
Code = 0x0
Source - Line : 0; Char : 0
Error Description = (null)
Not very helpful! However, the report does seem to be generated OK.

Can anybody shed any light on this or suggest a way of making it work without the error message?

Thanks,
Richard

[Uffe]

I believe that's the error message you get when your custom selection returns no rows for the fragment to work on. Which in turn may be due to a problem in the SQL query.

Maybe try with apostrophes instead of quotation marks? Perhaps your database is in ANSI quotes mode?
Other than that, the query looks fine to me.

/Uffe

[Richard Burke]

Thanks Uffe. My first thought was that there might be something wrong with the query but I tried it in the search window and it was fine. The fact that it is also displaying the report correctly is also an indication that it is not an issue of returning no rows.

Regards,
Richard

[Richard Burke]

Maybe I could put the question slightly differently:

If you were using Master / Model Documents and you wanted to include the Glossary as a Model document but only for parameters and definitions, how would you do it?

My approach is as follows:
1. Create a fragment with a custom tag. Put the SQL I included earlier in the Custom Query section.
2. Create a template with a package tag. Drag the fragment from step 1 inside the package tag.
3. Create a master document and add a model document to it.
4. Set the RTFTemplate of the model document to the template created in step 2.
5. Drag a package from the browser onto the model document. I chose the same package that the master document sits in. If I don't add a package nothing comes out. It doesn't seem to matter what package I drag on, so I selected one that requires minimal analysis by EA.

It's a bit convoluted but means I can tag the glossary on to the end of any report.

Thanks,
Richard

[Richard Burke]

I haven't changed anything and suddenly it has decided to work! I guess the question is answered

[Geert Bellekens]

Richard,

Also make sure you are using the latest version 12.1.1230 as that contains an important fix for the rich text fields in SQL and Script fragments.

Geert

[Richard Burke]

Thanks for the advice, Geert. I had a slightly earlier version installed so that might have been the issue.

Richard