Datasource Parameter - Gateway Connection Problem

[jwmarchetti]

I use parameters to define sql datasources so that I can develop against a dev/test db and then switch over to production when development is complete.  I setup gateway connections for both server/db combinations and the change the value of the parameter to alternate between.  This has always worked fine for me in the past.

I am currently having a problem connecting to a production server's datasource because the server name has a backslash in it (i.e. Servername\Secondnamepart).  The gateway connection is not being recognized and it appears that is because the PBI services is interpreting the backslash as a double-backslash.

I get an error message that the gateway is not configured correctly and the SqlServer connection shows an error that there is no available gateway for:

SqqlServer{"server":"Servername\\Secondnamepart","database":"dbName"}

I don't know why the backslash is doubled when the services is trying to identify a gateway connection.  Could somebody please help me with this?

Thanks,

Joe

[Greg_Deckler]

It's probably trying to escape sequence the backslash. You really, really, really should not put back slashes in server names. That is an awful idea.

[jwmarchetti]

That isn't very helpful.  I don't have any control over what the infrastructure team named this server several years ago.  Obviously, if I was naming it I would not insert a backslash in the name.  I was hoping for suggested solutions.  Thanks for commenting though.