Is there a reason that an expression like this would work fine if manually put into a number of reports, but not if saved as a global expression and put into the report as a saved expression?
[Invoice Date: Sum: Sales <EVAL!GetPromptValue('Reporting Currency','USD')!>]
I'm doing this to allow users to choose a reporting currency as a filter, and it works totally fine if I build the expression in all of my reports. I thought if I saved the expression globally it would make things simpler, but it stops working if I do that. Either way is ok, I can keep doing it manually - just wondering if there is an explanation or if this is unexpected behavior.
