It is probably more of a case that either {Asgnmnt.DATEACKNOW} or {Asgnmnt.TIMEACKNOW} are not in a format that the date function ot time function can convert.
Please post some sample date of the each of the 2 fields so that we can see the format of the date and time. I am sure a solution can be formulated after that.
Once I'd got two datetime fields, I then used the following formula to work out the difference in minutes:
@R to A Diff
datediff("n",{@DT Received},{@DT Acknowledged})
Lastly, I used the following formula to separate the values into days, hours and minutes - although, so far this hasn't worked. For example, I am getting "12 days, 0 hours and 0 minutes" for some differences that are only a day or two days.
numberVar dur := {@R to A Diff};
numberVar days;
numberVar hrs;
numberVar min;
stringVar result;
days := Truncate(dur/480);
hrs := Truncate(Remainder(dur,480)/60);
min := Remainder(Remainder(Remainder(dur,480),60),60);
So apart from the above formula not returning the expected results, when I try to navigate around the report, I get an error saying "bad date format string" - it opens the formula editor with the @Date Acknowledged formula.
am pretty certain is has something to do with null values within the acknowledged date. But - I have to include these values as there will be lots of calls received that have not yet been acknowledged, so therefore there WILL be nulls....not sure if i'm barking up the wrong tree - but if there was a way that I could tell Crystal to ignore any null ones then that might work...any ideas?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.