In the "Create Reports" exercise on page 105 of the ml6 pdf (page 109 of the pdf file) it has you create a Report Definition Selected Medical Plans.
In step 7 it shows a screenshot of the warnings and advises you to optimize .WaiveMedical and .MedicalPlan.Name. The screenshot shows .MedicalPlan.Name without any mention of the substring function used.
In my application, it shows
These properties are not optimized, and filtering or grouping by them will result in very poor performance: @@pxSubstring(.Medical.Name,"1","20")
So optimizing .Medical.Name does not remove the warning?
*Note my page property is called .Medical rather than .MedicalPlan
it may just be the way I am reading that exercise, but something seems off, or odd, about that exercise. Let me work up a new solution following those steps and I will report back my results later this afternoon. Will that be OK?
p.s. if anyone else reading this has an answer straight-away, please don't hesistate to post.
OK, I wanted to get back to this before the day ran out. The good news is it's not you - it's the exercise. We definitely need to make sure we can correctly optimize properties for reporting but, for now, you can set these warnings aside.
Let me write up something meaningful and post it here later.