Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
6 years ago

Jan 2020 multi value Param Problem

Hi all,

 

anyone experienced the following behavior in Jan 2020 update?

I have a multi-value parameter param and another parameter @ParamOpt

in the query for the dataset it looks like:

select * from table where ID = @ParamOpt

when I run the query I get an wired error message, so I checked in the query profiler and there I see

select * from table where ID = N'value1',N'value2'Opt

this didn´t occur before and seems to be a topic in Jan2020 release.

 

Best regards,

Thomas

BUG
Jan2020
multi-value
parameters

6 Replies

  • messerjc's avatar
    messerjc
    Advocate IV
    6 years ago

    I'm not in a position to test on our system, but just curious if you've tried 

     

    select * from table where ID = (@ParamOpt) 

     

    and if that gives you any different results? I have a vague old memory about parentheses being the proper form? Might not make a difference though...

    • Anonymous's avatar
      Anonymous
      Not applicable
      6 years ago

      No this doesn´t solve the issue. The Params were obviosly replaced or inserted via string replace and there is something different compared to old versions.

      • d_gosbell's avatar
        d_gosbell
        Super User
        6 years ago

        This is apparently a bug which the product team are aware of and they are working on an updated Jan download.   I don't think they have a specific timeline for when this will be available, but they do want to get it out as soon as they can. (so keep checking the date of the relase at https://aka.ms/pbireportserver and see when it changes from Jan 27th)

         

        In the short term the only work around I am aware of is to rename your parameters so the names are not a subset of each other. (eg if you rename param to @Param1 it will no longer "overlap" with the start of @ParamOpt)