Clarity

  • 1.  Export to Excel Portlet Hierarchy - Clarity

    Posted Nov 04, 2011 05:05 AM
    Hi,

    I want to know if with Version 12.1 of Clarity, when you export to excel a portlet hierarchy,
    all data is exported or is it only exported the ranks of the first level?.

    Thanks!


  • 2.  RE: Export to Excel Portlet Hierarchy - Clarity

     
    Posted Nov 08, 2011 05:00 PM
    HI All,

    Any ideas for this one?

    Thanks!
    Chris


  • 3.  RE: Export to Excel Portlet Hierarchy - Clarity

    Posted Nov 22, 2011 01:32 AM
    If case you are still at it
    tried Steve van Arsdale's portlet (see CA Tuesday Tip: Hierarchical Grid Portlets - part 1 ) in 12.1.2.1260

    That only exports the parents and not the children even if they are expanded.
    The same result for Export to Excel and Export data only.

    Martti K.


  • 4.  RE: Export to Excel Portlet Hierarchy - Clarity

     
    Posted Nov 29, 2011 08:04 AM
    Hi,

    Were you able to reach a resolution? If so please post so this thread can be marked as Accepted Solution.

    Thanks!
    Chris


  • 5.  RE: Export to Excel Portlet Hierarchy - Clarity
    Best Answer

    Posted Aug 15, 2012 09:13 AM
      |   view attached
    Ran across this thread while looking to see if someone had a hierarchical project portlet ready to share. So, the following and attachment are a bit late, but hopefully helpful to someone.

    Kathryn Ellis (CA) helped explain hierarchical portlet design to me. The attachment describes how to build such portlets, and how to include a section that exports the expanded listing to Excel. Basically, there's a flag set when one hits the Export to Excel selection, which causes an "Excel" section of the SQL to be executed - this section is designed to be 'expanded' and so the results in Excel are the expanded list's results.

    Dale

    Attachment(s)



  • 6.  RE: Export to Excel Portlet Hierarchy - Clarity

     
    Posted Aug 27, 2012 07:08 PM
    Thanks Dale!


  • 7.  Re: RE: Export to Excel Portlet Hierarchy - Clarity

    Posted Jul 21, 2014 02:39 AM

    Thanks Dale, that someone would be me!

     

    My NSQL Where clause now looks similar to:

     

    WHERE

    (@WHERE:PARAM:USER_DEF:INTEGER:hg_all_rows@ = 1)

    or

    OZ.this_rows_parent_row =

    (

        case when @WHERE:PARAM:USER_DEF:STRING:hg_row_id@ is null

        then '0'

        else @WHERE:PARAM:USER_DEF:STRING:hg_row_id@

        end

    )

    AND      @FILTER@

     

    Cheers,