This topic has been moved to Reporting.

https://www.cognoise.com/index.php?topic=38483.0

Quote from: Good Friend on 27 Jan 2026 02:01:52 PM2.  When you test that column, what does the data look like?
    In CSV the format changes to YYYY/MM/DD

No, when you test that column in CA, preferably in the modelling tool which you are using.  Also, when you test that column in your DB's administrative tool.

The object of these exercises is to identify where in the chain things go wrong.

Quote from: Good Friend on 27 Jan 2026 02:01:52 PM3.  If you use the cast function to cast the column to date what does the data look like?
    I casted it to varchar and HTML AND EXCEL gives YYYY-MM-DD which is the desired format but users are running this report in CSV and exporting it

No, when you do the cast it to date and view it in CA.  Also, why, if your column is a date data type, are you casting it to varchar?

Off the top of my head I don't know what variations native date data type columns can have for each DB vendor.   Certainly if it is cast to date in Cognos it will be rendered in the ISO 8601 format, which is YYYY-MM-DD.

Hi Everyone,

I have a report (403b) i have been building and adding features too as I learn and want to know if it could be optimized in report studio.  It is currently at 5 minutes and I want to add comparisons to the prior month.  I tried some of the property panels but was not able to notice a difference and I am not sure if I am doing it correctly.  (Concurrent, Use sql with clause, Data Base only, Join filter to in).  At the description level these seemed easy to understand but they didn't work enough to notice.

The report has 3 main queries + prompt queries + render features. The 3 main queries are Gross earnings, Point in Time for EE Status and Point in Time for Dept.  I used 2 joins 0:1 on both sides to create the final query with the correct amounts. A picture of the queries is attached.

Any tips or better articles to read would be greatly appreciated. Or if this seems like an appropriate time for this.  I don't have much to compare it too.  I am working in UKG, IBM Cognos Analytics with Watson 11.2.4

 

Still didn't answer the questions.

2. So, you're viewing the output in Notepad and the format of that column is YYYY/MM/DD?

4. Opening the CSV how?  Is the user opening the CSV file in Notepad?  Or are they allowing Excel to mess up the data?

I'm sorry if I couldnt answer your questions properly earlier.

1.  What is the data type of the column which is the source of your data?
     Using Current_Date so it is a DATE data type

2.  When you test that column, what does the data look like?
    In CSV the format changes to YYYY/MM/DD

3.  If you use the cast function to cast the column to date what does the data look like?
     I casted it to varchar and HTML AND EXCEL gives YYYY-MM-DD which is the desired format but users are running this report in CSV and exporting it

4.  Can you answer Doug's question.  Are you using a text editor to look at the CSV output?
     They are downloading the CSV file and opening the .CSV as is

Hi all, pleasure to have found this community.

Is anyone hiring these days? Finding roles hard to come by. I have 20+ YOE. Looking for something stable. Any leads? Let me know.

That's some deep mining, digging up a question from 16 years ago...

It looks like everybody was working really hard on this.  It's much easier.  You just need to make FM notice that a change has been made.

If your query subject expressions is...

select * from [blah]
...you just need to edit it somehow.  I usually add a space...

select *  from [blah]
Now FM knows it changed.  Click OK.

New column added.

QuoteYou are not answering the questions.

That is correct.  Still unanswered...

QuoteNot working for CSV?  Or not working for Excel?  Excel doesn't understand CSV files.  You might try looking at the result in a text editor.

Basically, if you're using Excel to open a CSV file, you're doing it wrong.
And if the requirement is to display data in Excel, use the Excel output format, not CSV.

This approach worked for me!
1. Click on Query Subject
2. Tools > Update Object

My table was indeed select * from [blah], so no concerns from me on potentially old fields being removed via the Update.

Thanks - kind of funny to find a 15 year old thread that solves my problem in 2026 :)

Quote from: bloggerman on 19 Aug 2010 03:35:38 PMI believe there is another way to it..The one mentioned above should work as well....Click on the Query Subject....Under Tools tab click the "Update Object" option and that should update the Query Subject with latest metadata information from the database. Try it out and let me know if it works.

Quote from: cognostechie on 19 Aug 2010 03:41:33 PMYes, Tools/Update Object is the right way to do it. However, keep in mind that by doing this, if any column has been deleted from the Table, it will also be deleted from the Query Subject

You are not answering the questions.  I don't know if that is because you don't understand them or not.  Your responses lack sufficient context. Please do try to answer the questions.