Deploying Dash+QaaWS queries to a remote crystal server

[pulseguy]

We develop our xcelsius dashes on a local qaaws server. We deploy them to various client servers after development - which requires creating localised versions of each dash, connected to *their* server instead of our dev server, and reexporting the dashboard.

Is there a way to make this transparent to the dash?

Playing around with the "web service URL" field in the Data Manager has yet to yield results - with load-from-spreadsheet, even if it works as it seems to be intended, its still uses the old server for the WSDL url - which is on our vpn, and not the clients. On top of this, as of yet, I have been unable to successfully test a case of using two different queries on the same server - it appears that the dash uses the WSDL url for the web service instead of dynamically loading from the 'Web Service URL' field - as whichever url is used for the WSDL Url is the query that gets run even if the 'Web Service URL' is contradictory.

Any ideas / suggestions?