Hi Anisha,

In response to ...

Q: "Is this field [Case Distributions, Backlog & Closures Picker]  in string or integer format?"

A: this field [Case Distributions, Backlog & Closures Picker] is a String List Parameter.  So this calculation contains [Case Distributions, Backlog & Closures Picker] parameter.

After you asked me about Data Type of the Parameter field, I quickly realized that I had entered my Parameter Values as string names (such as Assigned to CSR Today GMT, etc.) in the "List of Values" field.  I should have entered integer Values 1, 2, 3 as I had referred these Values in my Calculation by integer instead of by string names (such as Assigned to CSR Today GMT, etc.).

Because of this error the calculation did not recognize integer Values in the Parameter because the Parameter referred to the Values by string names (such as Assigned to CSR Today GMT, etc.) instead of integer Values. 

This question helped me understand that the issue with the calc field was in the Data Type as well as List of Values selections I made while creating the Parameter.

Thank you so much for your help with this an my other question!

Manuel

Hi Deepak ... correct, trying to say that if whatever is in yellow (the Parameter) 1, 2 or 3 then execute that that calculation.

Initial error message was: Expected type string, found integer. Comparison in 'CASE' expression must be string type.  Even though my 'CASE' expression Parameter [Case Distributions, Backlog & Closures Picker] was already a String, I ended up changing the Parameter Data Type from String to Integer as well as changing Values (such as Assigned to CSR Today GMT, etc.) to 1,2,3 and the Calculation is now valid. 

FROM:

TO:

Thank you so much for your help with this question!

Hi Anisha ... Thanks for recreated the scenario with SuperStore.

Even though my 'CASE' expression Parameter was already a String Data type (as you can see from the Parameter print screen below) I converted the 'CASE' expression Parameter in the Calc Field using INT() and the calculation is now valid. 

     CASE INT([Case Distributions, Backlog or Closures Picker])

However not sure I understand the error message which stated, "Expected type string, found integer.  Comparison 'CASE' expression must be a string type."  I created the Parameter as a string, which is what was expected according to the error msg.  But then in the Calc Field I converted the  'CASE' expression to INT:  CASE INT([Case Distributions, Backlog or Closures Picker]) which doesn't make scene to me since the Parameter used in the 'CASE' expression was created as a String to begin with.  Why does it need to be converted to INT in the Calc Field when according to the error message the expected type is string and that is what was created? Any guidance with this part of the question would be greatly appreciated. Thank you.

Converted 'CASE' expression to INT below and the Calc is now valid, even though the error message stated that the expected type is string and that is what was created?

      CASE INT([Case Distributions, Backlog or Closures Picker])

Thanks for this input also.  I learned that for my scenario, I can change the Parameter's Data Type to

Integer ...

... and when I do then I do not have to convert the 'CASE' expression into INT().

Thanks again Deepak!

Oh I see, got it.  Thanks again for all the valuable tips and info. -Manuel