Forum Discussion
Measures based on Lookup
Will still work as a KPI, your table relationship will handle all of the filter contexts. Using the calculate statement with the filter is not doing anything.
Dear Ross,
Wow will it works by creating the measure sum(CollectionAmount)in Billing table?
You could actually get away without using the measure at all and just putting the field inside the visual and then creating the filters or context from the billing table on your report.
If you do create it as a measure, the measures home table should be the same table as the field you are summarizing. The filters, which are sitting in the Billing table, are what will make use of the table relationships to give you the correct answer, based on whatever context you pass.
For example, if your billing table has a "City" column and you want a sum for that city. When you use the city as your filter context, the table relationship will say "Ok, what records in the billing table do we have? Ok from those records, what records are linked in the collection table? Ok now we have a short list for the collection table, lets run the measure. This will sum the values in the amount column based on this filter context. Ok that is answer X".
Then when you change the filter to another city, it will do all of that again and give you answer Y.