DAY_ID.TIMESTAMP not avaiable in 2.0.0.2?
Hi,
I developed a report from WORKITEM_CHNGS table on RTC 2.0. We have upgraded to 2.0.0.2 and now when I try to run the report it throws an error saying "Column binding "DAY_ID.TIMESTAMP" has referred to a data set column "DAY_ID.TIMESTAMP" which does not exist".
I checked the design file and tried to edit the data set and now I dont see "DAY_ID.TIMESTAMP" in the avaialable columns.
Any clue?
Thanks,
Bharath
I developed a report from WORKITEM_CHNGS table on RTC 2.0. We have upgraded to 2.0.0.2 and now when I try to run the report it throws an error saying "Column binding "DAY_ID.TIMESTAMP" has referred to a data set column "DAY_ID.TIMESTAMP" which does not exist".
I checked the design file and tried to edit the data set and now I dont see "DAY_ID.TIMESTAMP" in the avaialable columns.
Any clue?
Thanks,
Bharath
3 answers
Hi Bharath,
Sorry for the inconvenience, The DAY_ID field was only supposed to be used by the two views WORKITEM_CHNGS_TO and WORKITEM_CHNGS_FROM to count the number of changes during a day. The DAY_ID value can be extracted using very simple math from the TIME_ID value.
Rafik Jaouani
Ok. But it was there in 2.0 for WORKITEM_CHNGS right? I have the similar purpose of displaying count of Workitems on a crosstab, for example, that are reopened on a particular day. With TIME_ID it displays a new row for each reopened WI. Please suggest a work around.
--Bharath