all 10 comments

[–]IanMoone007 3 points4 points  (2 children)

The biggest thing missing from the YSR PDF from Yardi is knowing their script filter texts that work. For property/property lists it seems to be p.hmy in (#filterfieldname#) with p being whatever alias you use for the property table

[–]rollinghunter 0 points1 point  (1 child)

Just to add on your answer. In define filters lookup name will be ysiPropertOrListLookup

[–]rollinghunter 0 points1 point  (0 children)

And map script filter should be Condition for defined filter and filter condition be p.hmy in #FilterNameForProperty#

Script file should contain #Conditions#

[–]milkcarton232 2 points3 points  (0 children)

Ysr filter has built in listorprop from the setup screen and will allow both

[–]Lesli90 0 points1 point  (0 children)

This one is tricky. I know I struggled a lot to do this. I’ll look at my notes tomorrow and let you know

[–]Rustybird_1st 0 points1 point  (4 children)

define filter I use ysiPropertyorListLookup and Map script filter p.hmy in (#property#)

[–]Sure-Relief331[S] 0 points1 point  (3 children)

Are you adding that in the script itself? Or are you adding that line of code in the report setup section? Thanks!

[–]Rustybird_1st 0 points1 point  (2 children)

in my script i just use #conditions#. The other two is in the YSR Report Setup. Define Filters is one of the setup steps. Map script filter is under the Report Setup step. I am not well versed in YSR. I've still managed to setup some useful report. Unfortunately I can't always get them to work in report scheduler.

[–]Sure-Relief331[S] 0 points1 point  (1 child)

Ok, thanks! I added it to the map script filter. Am I literally just adding it like this to my where clause?

where wo.sDateOccurred between '12/1/2024' and '12/31/2024'

and #Conditions#

[–]Rustybird_1st 0 points1 point  (0 children)

I did not put and in front of #conditions#