Parameters in calculated field

Question & Answer
, , ,
1

Hi,

I’m creating a calculated field using parameter. The parameter will have values Month 1, Month 2 and so on. Month 1, month2 .. represents the forecast submission month. I’m using this parameter as a filter. If the user selects Month 1 from the filter then I want to display the forecast that was submitted for the selected month. I have submission_month field in my dataset. How can I create a calculated field to show this. Can I compare with ‘=’

2

Hi @chgo,

You can use the “=” operator with parameters. You can see an example in the screenshot below.

image
image440×149 2.98 KB

3

When I do ifelse(${parameter_name} = {field_name},{revenue},null) I get the following error -“Expression {{argumentName}} for function {{functionName}} has incorrect argument type {{incorrectArgumentType}}. Function syntax expects {{functionSignature}}.”

4

${parameter_name} refers to the value of a parameter. Can you rewrite it this way?

ifelse({field_name} = ${parameter_name},{revenue},null)
5

parameter_name doesn’t refer to parameter value, it is the parameter. I’m using parameter as a filter. So that when user selects month1 only forecasted revenue submitted for that month will be displayed. This comparison is needed because I’m also showing actuals data for month1 -1 based on month1 as the selection in the filter.

6

Hi @chgo,
In regards to what David mentioned, when you include the parameter in a calculated field, you are essentially using whatever parameter value is selected in your calculated field, therefore, while it is the parameter, it is using the parameter value in the calculated field. Did you test out his suggested calculated field fix and if so, did it provide an error still or did it provide incorrect information?

As it’s been awhile since last communication, let us know if you’re still working on this or if you were able to find a work around in the interim.
If we do not hear back within the next 3 business days, I’ll close out this topic.

Thank you!

7

Hi @chgo,
Since we have not heard back, I’ll go ahead and close out this topic. However, if you have any additional questions, feel free to create a new post in the community and link this discussion for relevant information if needed.

Thank you!