Maximo

 View Only
  • 1.  Exporting CSV data from report: How to export report labels instead of DB column names?

    Posted Sun November 28, 2021 10:13 PM
    Edited by System Wed March 22, 2023 11:49 AM
    MAM 7.6.1.2:

    I have a report that users export data from.

    When Maximo exports the data to CSV, the DB column names are used as the CSV column headers, instead of the report labels.

    Is there a way to export the report labels instead?



    Thanks.
    #AssetandFacilitiesManagement
    #Maximo


  • 2.  RE: Exporting CSV data from report: How to export report labels instead of DB column names?

    Posted Mon November 29, 2021 08:49 AM
    I don't believe this is possible (at least today, not sure if something will change with the upcoming BIRT update). It's not the database column (it's the column as defined in the data set of the report) so you could modify that in the report to match the label but that's more work than it's worth in my opinion.

    I find this works well with a single set of data (list reports basically) so I typically try to move these into a result set instead and have them download it that way from Maximo.

    ------------------------------
    Steven Shull
    ------------------------------



  • 3.  RE: Exporting CSV data from report: How to export report labels instead of DB column names?

    Posted Mon November 29, 2021 09:26 AM
    Edited by System Wed March 22, 2023 11:48 AM
    Thanks Steven. I think I see what you mean -- about list views/table controls using the attribute titles when downloaded to Excel (good).


    An unrelated example:


    Your idea about "creating result sets instead and have them download it that way" is very interesting. As an example, I could create a new tab in WOTRACK and add a table control that shows all the records from my "task rollup view". Is that the kind of thing you had in mind?
    And I wouldn't need a flat file object structure for that, which is great. But I suppose, if the user filtered the WOs in the main WOTRACK list view, that filtering wouldn't be honored in my custom table control.





  • 4.  RE: Exporting CSV data from report: How to export report labels instead of DB column names?

    Posted Mon November 29, 2021 09:50 AM
    That approach makes sense if the data is related (IE you only want data from a child object that depends on the WO in this case). I wouldn't do it if the data was unrelated, even though that would be possible. 

    I typically use result sets on start centers when the object being reported against is the main object of an application. While you can use object structures for a result set, you wouldn't have to use them. I don't like people using the download data on the list tab of an application as it causes columns to get added to support that purpose that aren't used by traditional users. That clutters the list tab which I really dislike. And typically there are columns that they don't want that they have to delete from the export. A result set that contains just the columns you need with the default query you want (while still supporting the user applying additional filters) seems like a good solution to me when it can be used.

    ------------------------------
    Steven Shull
    ------------------------------



  • 5.  RE: Exporting CSV data from report: How to export report labels instead of DB column names?

    Posted Mon November 29, 2021 10:22 AM
    Edited by System Wed March 22, 2023 11:49 AM
    If this is for a simple, table report then you may want to try exporting the report using the Excel emitter option.  I believe that would use the report label.  (export report as opposed to export data)

    ------------------------------
    Steve Hauptman
    ------------------------------



  • 6.  RE: Exporting CSV data from report: How to export report labels instead of DB column names?

    Posted Mon November 29, 2021 11:01 AM
    Thanks Steve H. Good point.

    In my case, I was hoping to use the Export Data option, so that the data gets exported as a simple data table (without the extra formatting that comes with the Export Report option -- since users need to delete that stuff each time they download the file).

    Cheers.


  • 7.  RE: Exporting CSV data from report: How to export report labels instead of DB column names?

    Posted Tue December 07, 2021 11:20 PM
    Edited by System Wed March 22, 2023 11:44 AM
    Hi Steven,

    Regarding this blurb: "It's not the database column (it's the column as defined in the data set of the report) so you could modify that in the report to match the label but that's more work than it's worth in my opinion."

    To clarify, are you referring to the Value column in the Selected Fields table control in the Ad Hoc Report dialog?



    If so, it looks like the Value column is read-only in that table control. When you say I "could modify that in the report", how would I modify it if it's read-only?



    Thanks.




  • 8.  RE: Exporting CSV data from report: How to export report labels instead of DB column names?

    Posted Wed December 08, 2021 08:54 AM

    I don't think there's a way to control this on a QBR as it builds the underlying report for you. You could export the report, modify, and import it but then as a user makes a change it will be overwritten so I wouldn't do this for a QBR.

    When you do a custom report (or clone an out of the box report), you can define the output columns in the data set. For example, in the woprint.rptdesign the work order description is set as wodesc. I could change this to something more descriptive and this is what gets used on the export data. 



    ------------------------------
    Steven Shull
    ------------------------------



  • 9.  RE: Exporting CSV data from report: How to export report labels instead of DB column names?

    IBM Champion
    Posted Thu October 20, 2022 12:35 AM
    Actually, the secret is to define the Display Name in addition to the Name.  The export will then use the Display Name.

    ------------------------------
    ===============================
    Craig Kokay,
    Lead Senior Maximo/IoT Consultant
    ISW
    Sydney, NSW, Australia
    Ph: 0411-682-040
    =================================
    #IBMChampion2022
    ------------------------------