I am using a!queryProcessAnalytics() to get data from a portal report.

...own above. That filter alone looks like the below code. In the below code, the rule P360_RULE_Conversion_dateToDatetime is basically doing the same as userdatetime(). So my question is if anyone has another solution to the problem presented here or if this is the best way of doing it. Let me know if I need to clarify what the problem and my solution is.

if(
and(
ri!startDatetimeMin = ri!startDatetimeMax,
or(
not(
isnull(
ri!startDatetimeMin
)
),
not(
isnull(
ri!startDatetimeMax
)
)
)
),
a!queryFilter(
field: ri!fieldName,
operator: "between",
value: {
rule!P360_RULE_Conversion_dateToDatetime(
date: ri!startDatetimeMin,
hour: 0,
minute: 0,
second: 0
),
rule!P360_RULE_Conversion_dateToDatetime(
date: ri!startDatetimeMax,
hour: 23,
minute: 59,
second: 59
)
}
),
{
if...

...(
isnull(
ri!startDatetimeMin
),
{},
a!queryFilter(
field: ri!fieldName,
operator: ">=",
value: rule!P360_RULE_Conversion_dateToDatetime(
date: ri!startDatetimeMin,
hour: 0,
minute: 0,
second: 0
)
)
),
if(
isnull(
ri!startDatetimeMax
),
{},
a!queryFilter(
field: ri!fieldName,
operator: "<=",
value: rule!P360_RULE_Conversion_dateToDatetime(
date: ri!startDatetimeMax,
hour: 23,
minute: 59,
second: 59
)
)
)
}
)

Hi erickp,
please use below code snippet

a!queryFilter(
field: "c8",
operator: "between",
value: {today(),today()+1}
)
let me know if this works.

Yes @venkateshamu. That is another alternative of doing it. Thanks. Any other suggestions?

The Appian conversion function todatetime() could be used to accomplish this. The only catch is that whenever a date is converted to dateTime, it is initialized at 0:00:00. So your code will need to look something like this:
value:{todatetime(ri!date), todatetime(ri!secondDate + 1)}
The +1 pushed the date forward by one day, which solves the issue you had if the user selects the same date.
forum.appian.com/.../Conversion_Functions.html

@erickp: For a similar scenario we are using rule as given below. Almost same as what you have done. We just made it generic to call from multiple reports. All our reports have start and end date filter and we face similar issue when user selects same date.

Rule: Report_getConvertedStartDateTime

/* -- inputDate_dte rule input is of type DATE -- */

with(
\tlocal!formattedDate: text(ri!inputDate_dte, "mm/dd/yyyy HH:mm z"),
\tlocal!splitFr: split(split(split(local!formattedDate, " "),"/"),":"),
\tuserdatetime(
\ tlocal!splitFr[3],
\ tlocal!splitFr[1],
\ tlocal!splitFr[2],
\ tlocal!splitFr[4],
\ tlocal!splitFr[5],
\ t"00"
\t)
)

=========================

Rule: Report_getConvertedEndDateTime

/* -- inputDate_dte rule input is of type DATE -- */

with(
\tlocal!formattedDate: text(ri!inputDate_dte, "mm/dd/yyyy HH:mm z"),
\tlocal!splitFr: split(split(split(local!formattedDate, " "),"/"),":"),
\tuserdatetime(
\ tlocal!splitFr[3],
\ tlocal!splitFr[1],
\ tlocal!splitFr[2],
\ tlocal!splitFr[4],
\ tlocal!splitFr[5],
\ t"00"
\t) + intervalds(23, 59, 0)
)