Clarity

Hi Martti,

sorry for replying to this older post but my question belongs pretty to this topic.
I've the same issue like user above, different finish_dates in Clarity and Database. After read some threads I've realized,

I have to use COP_CALC_FINISH_FCT Function as you've recommended. So there is my question/problem:

I have to add this function to portlet which shows data in Clarity.
(screenshot from different finish dates)

However this portlet (in our Clarity in Home -> Projects -> Project list) gains data only from 'project' object, it means,

there is no such SQL code behind it.

I suggest it's some standard Clarity functionality(standard portlet), so there

should be adjusted some .xbl or other file directly in server. Do you think I'm right or do you have some other suggestion for my issue?
Your help is very appreciated. Thanks

Matej

Are you sure there is a problem here?

The original question was why the "database date" differed slightly from the "clarity date" - the answer was that we need to apply that function to the "database date" in order to get the "clarity date".

In your example / screen shot, you show that the "database date" is different to the "clarity date", but thats all OK, because the portlet is showing the "clarity date".

i.e. only need to apply the function when we are manipulating the "database date"

Hi Dave,

Thanks for quick reply, I thought that the "right date" is stored in database and in Clarity is different, so that's why I'd like to show date in Clarity which is in DB.

We are also using some Excel sheets for Business needs. Source data of these Excel files is Database so there always appear end dates like it's stored in the DB

and people are wondering why some project's end dates are different there and in Clarity....

I'm wondering why this happened now (I guess from new year 2015), because I've remember issue like that in the past.... May I ask If you have some suggestion,

what could cause that this issue somehow "appear" now? Many thanks for your response!

Matej

The "right date" is the "clarity date" (and not the database date).

The issue is that Clarity stores the right date in a way that makes it non-obvious if we read it directly from the database through SQL, the solution to that is the function.

The method that you are extracting data for use in your Excel spreadsheets is where you need to use the function then. Presumably if you were using a standard object XOG-read to populate your spreadsheets then the date would be "right" but using (for example) a Query-API read where you have "coded" the SQL would need to use the function, as would any "plain SQL" method that you might be using.

Hi Dave,

OK, so in Clarity is the "right date".

In these Excel sheets Database source is another DB as Clarity use. There are used some job which loads all Clarity

data from Oracle(Clarity) DB to MS SQL DB(used for Excel reporting). The problem I've maybe not mentioned before is, tha this job has created by a 3rd party company

and we didn't modified it.

As I said, before, in year 2014 the dates were the same. Also I've never noticed that dates are different in Clarity and in DB when querying. It start as of now, from year 2015...

Matej

Ok well I can't explain at all why you think that the dates were OK / consistent  in the past and that they are not now - all I am saying is that that 3rd Party extract is where you would need to apply the function (which I suspect doesn't help you at all).

Hi Dave,

Yes, you are right, thank you a lot for your hints.