Book a Demo

Author Topic: RTF report for customSQL search results - fails  (Read 3591 times)

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
RTF report for customSQL search results - fails
« on: September 23, 2008, 05:00:40 pm »
You're supposed to be able to generate an RTF report for selected items in a search.

Once the search generates output, you can select one or more of the items and then using the <Search Item Context Menu>|Documentation... generate the report.

When I select either of the options under Documentation... the RTF Generation dialog doesn't come up as it's supposed to.  Since I've previously had problems specific to my machine/environment; before I report a bug, can anyone confirm/deny that the dialogs do come up for them?

If the dialog does come up, are you able to generate a document successfully?

How are the results from the search linked to the document templates?  I've made the assumption - since i can't see it explicitly documented anywhere that I use the Element level fields in the template to map to the fields returned by the search.

BTW: setting up a Model Document (Virtual) - with search also has the generation fail - without any explanation (other than "Generation Failed").  I suspect for the same reason (that the dialog or API) doesn't come up.

<EDIT>
When I first posted, I forgot to mention I was using a custom SQL query to return the search list.
I've been able to generate RTF output for Query Builder searches.
But I am interested in using custom SQL searches...
</EDIT>

I'm using EA 7.1 (832) on Windows Server 2008 (64bit)

TIA,
Paolo
« Last Edit: September 23, 2008, 06:37:37 pm by PaoloFCantoni »
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Re: RTF report for customSQL search results - fail
« Reply #1 on: September 24, 2008, 08:12:18 am »
In order to use any EA functionality with a custom SQL search, you will need to return the guid and type of the object found.  This is described at http://www.sparxsystems.com.au/EAUserGuide/index.html?creating_filters.htm, although it doesn't explicitly mention reporting.

eg. SELECT ea_guid AS CLASSGUID, Object_Type AS CLASSTYPE, Name FROM t_object

It sounds like there is a user interface issue here that it isn't letting you know what's wrong though, so go on and report the bug.

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: RTF report for customSQL search results - fail
« Reply #2 on: September 24, 2008, 11:58:11 am »
Quote
In order to use any EA functionality with a custom SQL search, you will need to return the guid and type of the object found.  This is described at http://www.sparxsystems.com.au/EAUserGuide/index.html?creating_filters.htm, although it doesn't explicitly mention reporting.

eg. SELECT ea_guid AS CLASSGUID, Object_Type AS CLASSTYPE, Name FROM t_object

It sounds like there is a user interface issue here that it isn't letting you know what's wrong though, so go on and report the bug.
(My emphasis...)

Thanks Simon!

That did the trick...

Perhaps Roy could weave his magic and make this more prominent.  Also, the statement about a package list OR a search.  This stumped me for a while...

I'll pop a bug report in about the non-explicit dialog.

Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

RoyC

  • EA Administrator
  • EA Practitioner
  • *****
  • Posts: 1297
  • Karma: +21/-4
  • Read The Help!
    • View Profile
Re: RTF report for customSQL search results - fail
« Reply #3 on: September 24, 2008, 04:01:13 pm »
I have updated the Help in a number of places to highlight the point about SQL searches. Changes should be visible at the release of the next build.
Best Regards, Roy