We are using version 3.1
We have also thought about using IN in sqlQuery rather than in CAML but the problem is we have to extract the large set of value from CAML first then only we can filter in sqlQuery which takes longer time. This would be the last resort if we do not have any other way of doing this. Any idea if we still have other workaround?
And to answer your questions.
My query as below
Approved
@ISOTimesheetStartDate!
@ISOTimesheetEndDate!
@EmployeeID!
@CostCentre!
@Department!
@ISOSubmissionStartDate!
@ISOSubmissionEndDate!
@ApprovalStatus!
@ProjectCode!
@WBSCode!
@ISOTimesheetStartDate!
@ISOTimesheetEndDate!
Select Department, CostCentre,Timesheet.EmployeeID as EmployeeID, EmployeeName, ActivityType,ProjectCode, ProjectDesc, WBSCode, WBSDesc, Rate, Period, TimesheetDetails.Date as Date,
NoOfHours, Overtime, ApprovalStatus, SubmissionDate,
Round(NoOfDay+NoOfOTDay,2) as TotalDay,
Round(NoOfDay+NoOfOTDay,2)*Rate as TotalCharge
from Timesheet
INNER JOIN TimesheetDetails ON Timesheet.Title = TimesheetDetails.Title
WHERE (NoOfHours != 0 OR Overtime != 0)
WeeklyTimesheet
How many values do you have for your multi-value parameters?
** up to 400
What's the most common scenario when a user run this report: select one value? a few values? Select All values?
** few values and all values, there are different group of users for this report, some users from department A always select all, but others only selevt a few
Is there any possibility to use cascading dependant parameters to break down this long list into 2 parameters (master-slave)?
** Is not a master slave relationship, so cannot be broken down.