Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
5 replies
Subscribers
5 subscribers
Views
1873 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Reports
45276 - no subject - I have a report over around 650 running
joel
over 11 years ago
I have a report over around 650 running processes. In one column I am doing the following calculation calworkdays(pv!date,today()) in the majority of cases this works fine, in some cases it does not despite pv!date have a value. The strange thing is if I apply a filter on another column it works fine. Remove the filter and the same cases break. If I change the calculation to today-pv!date, then the whole thing works fine. Any thoughts to why this behaviour might be happening. When I look at the report timing the report is running in 0.112 seconds and the only thing I can see is Case Age(Working Days) (EVAL:@reason=Function calworkdays: domain) in Name column Type: Column (Error) Resources:process-analytics2. Any thoughs...
OriginalPostID-45276
Discussion posts and replies are publicly visible
0
dbabu
over 11 years ago
Is your PV named date? And has the type of the PV changed at any point, i.e. say initially from date/time to more recently to be date? I am thinking maybe some instance has an incorrect value for this PV and it might be only for specific rows that this function is throwing the error.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
joel
over 11 years ago
Hi Dinesh, thanks for your reply. I thought it was a data issue at first. My collegue who built the process tells me that data type has never been changed. I also checked they all have values as dateTime, and have tried wrapping the pv! in a todate() expression with the same result. The bit that really confuses me is that if I reduce the cases via a filter it works fine, remove the filter and the same cases break! I also tried networkdays() and this causes the same issue.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
dbabu
over 11 years ago
Couple more points I can think of that could help troubleshoot this further:
1. Instead of passing the pv!date to the calworkdays function, can you pass in say, the process start date. This will help identify if the issue is with the data, or the number of rows and such
2. Can you try the same function on a report for another process which has a date variable?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
joel
over 11 years ago
Yep, thanks! Swapped the date to pp!starttime and that worked, so it could be a data issue. Strange thing is in another column that variable calculates no problem when not using the calworkdays or networkdays functions
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
joel
over 11 years ago
I have worked out that it is everything running on Exec engine 02. Does anyone know if there are any ways to stop this happening or resolve this issue.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel