PS Query & SQL

 View Only
  • 1.  Composite Query Field Reordering

    Posted 02-28-2025 04:29 PM

    Hello all,

    I just added an Idea Lab: Field Reordering Improvement for Composite Query.   Here is what I am asking:

    Please provide a way to reorder the fields for Composite Query rather than using the Action icon and moving the field up or down one step at a time for each click. This can take an inordinate amount if you have many fields that will be used in the output.

    For instance, if I have 80 fields and add a new field, it will be added at position 81. Say I want to move that field to position 40, then I have to click the Action icon > Move Up for every single step.

    Is there a way to create a drag and drop utility or even having the option to reorder fields as already exists in Query Manager.

    Please vote. Currently, having to use that Action icon to move the fields is less than ideal.



    ------------------------------
    Daniel Labrecque
    Senior 2 Business Systems Analyst/Functional Architect
    University of Nevada, Las Vegas
    ------------------------------

    Message from the HEUG Marketplace:
    ------------------------------
    Find, Review, and Engage with Higher Education-focused solution providers, products, and services using the HEUG Marketplace.
    ------------------------------
    Alliance 2026 Registration is Open!


  • 2.  RE: Composite Query Field Reordering

    Posted 03-02-2025 11:47 AM
    Daniel,

    I have never used composite query before for any report. However, i am looking forward to learning more about it. What are best case scenarios that Composite Query can help instead of  connected Query.


    I Voted.

    Mital Naik

    UT Arlington


     




    Alliance 2026 Registration is Open!


  • 3.  RE: Composite Query Field Reordering

    Posted 03-03-2025 06:25 AM

    Good Morning Mital - There are several differences in Connected Query and Composite query, but the primary idea behind the two is the same. Both tools allow users to combine (in various ways) the results of multiple queries.  Both tools can be scheduled, with output going to a mounted drive, to an email address or to Report Manager. 

    But, these tools differ in several important ways.  First, the UI is more user friendly in Composite Query.  It is easier and more intuitive, and once you become accustomed to how it works, it feels quite similar to Query Manager.  Second, Composite Query can create aggregate functions, expressions, and drilling queries  URLs.  This means you have the choice of creating some expressions in the initial queries, or in Composite Query as well as access to other functionalities.  Also, Composite Query can write to HTML, XML or Excel format, like Query Manager.  Finally, Connected Query produces XML output, and is used with BI Publisher. 

    The Use Cases follow from these capabilities. 

    • Connected Query is needed if you are creating a BI Publisher report. Or, it is often called upon if you need to create an XML file for an integration of some sort.  
    • Composite Query is useful if you are creating a specific report and you need the results written into a spreadsheet format.  It is also easier to tweek and update, if you know a report will need to be changed over time. 

    Take Care, and I am sure Dan will have other uses. 



    ------------------------------
    Tom Johnson
    Sr Business Systems Analyst
    Duke University
    tom.johnson@duke.edu
    "None of us is as smart as all of us"
    ------------------------------

    Alliance 2026 Registration is Open!


  • 4.  RE: Composite Query Field Reordering

    Posted 03-03-2025 08:06 AM
    Tom,

    This is helpful!  Would you please share a few examples of reports in which you currently use Composite Query at your institution?


    Mital Naik

    UT Arlington

     




    Alliance 2026 Registration is Open!


  • 5.  RE: Composite Query Field Reordering

    Posted 03-03-2025 10:13 AM
    Edited by Daniel Labrecque 03-03-2025 10:14 AM
    Hi Mital,
     
    Tom provided a great comparison of Composite Query and Connected Query. I've used both, and each has its strengths.
    Composite Query
    • I appreciate its flexibility, especially for handling large datasets. For example, I have one that returns over 80 fields from nine different queries, making it easier to build complex queries in manageable chunks.
    • However, the UI can be a bit clunky.
    • One important limitation: All prompts must be assigned at the Composite Query level, meaning the base queries cannot have active prompts.
    • To work around this, you might want to maintain two versions of your queries: one with prompts for data verification and another for use within the Composite Query.

    Connected Query
    • Unlike Composite Query, prompts can be assigned at the query level.
    • It supports XML output format and user-defined output format (XFORM), which allows for transformation using XSLT.
    • If you need the results in Excel, you can open the XML file in Excel, but you may need to make some formatting adjustments for better readability.

    Both have their use cases, so it depends on your specific needs. Hope this helps!



    ------------------------------
    Daniel Labrecque
    Senior 2 Business Systems Analyst/Functional Architect
    University of Nevada, Las Vegas
    ------------------------------

    Message from the HEUG Marketplace:
    ------------------------------
    Find, Review, and Engage with Higher Education-focused solution providers, products, and services using the HEUG Marketplace.
    ------------------------------

    Alliance 2026 Registration is Open!


  • 6.  RE: Composite Query Field Reordering

    Posted 03-03-2025 11:18 AM

    We use Connected Query in all of our pillars. It's great for creating beautiful, complex BI-Reports. Once you decide the layout of your report, you build that layout into your Connected Query tree. Later when you get to building your BIP template, the report practically builds itself. You do have to keep the layout of your final report firmly in your mind as you are building that initial tree, or it can get obnoxious going back and fixing that little thing you forgot.

     

    Composite query has only been available in DVL for us to play with. To me it functions like a query that treats other queries as tables. Since we've built a lot of great custom views over the years which are essentially queries that we can use as tables, this may be why we haven't found much use for Composite Query.

     

    I personally would like to have Composite Query available in PRD, but I have to prove I can't produce data in some other way. The justification of "it would be nice to have, just in case" doesn't really fly. I guess I shouldn't complain about having a ton of great custom views.

     

     

    Lynn Hutchins
    Application Development
    Information Services
    lynn.hutchins@cwu.edu

     

     

     

     

     




    Alliance 2026 Registration is Open!


  • 7.  RE: Composite Query Field Reordering

    Posted 04-11-2025 11:01 AM
    Thank you for the info, Daniel! Very helpful!

    Mital Naik

    UT Arlington

     




    Alliance 2026 Registration is Open!


  • 8.  RE: Composite Query Field Reordering

    Posted 04-12-2025 04:09 PM

    Hi Dan,

    This will be helpful. I voted.



    ------------------------------
    Tirumala Rao Chimpiri
    Senior Programmer Analyst
    Stony Brook University
    ------------------------------

    Message from the HEUG Marketplace:
    ------------------------------
    Find, Review, and Engage with Higher Education-focused solution providers, products, and services using the HEUG Marketplace.
    ------------------------------

    Alliance 2026 Registration is Open!