Forum Discussion

l2aFa's avatar
l2aFa
Helper I
8 years ago
Solved

Gateway connectivity issue

Hello everyone   I'm having a bit of trouble trying to get to work the following scenario:   - I have two machines, one is a production server with the gateway installed (let's call it A) and the...
Need Help
  • l2aFa's avatar
    l2aFa
    8 years ago

    Anonymous 

     

    No problem, glad to provide it :)

     

    I finally resolved it publishing the report from within the production environment and for future developments and maintenance this datasource will be accesed through the Power BI Service data connector like we discussed.

     

    Thanks for your help!

l2aFa's avatar
l2aFa
Helper I
8 years ago

Hi there Eno

 

Thanks for your answer.

 

Unfortunately, I can't match the Power BI service defined datasource from within the development environment (B) cause it cant see the production machine in the way the service does, so like you said, they will never match.

 

However, I'm gonna try to ask for deploying the PBIX from witihin the production server just once and then I'm gonna replicate it on B connecting through the Power BI Service defined datasource connector instead of referencing A directly. I didn't find any other way.

 

Thanks again!

Anonymous's avatar
Anonymous
Not applicable
8 years ago

l2aFa Maybe I didn't explain myself. I know the connection from the DEV machine to PROD won't work based on your description. But if DEV mirrors PROD, you can develop against DEV in the PBIX file. When you are done. You can alter the connection string in the PBIX in DEV to use the PROD connection. This will break the report. Publish to the Power BI Service. I assume, the report begins to work because the connection to PROD is valid. (Is this not the case?)

If you are locked into DEV, this is an extra step, but my assumption is that it would work...

  • l2aFa's avatar
    l2aFa
    Helper I
    8 years ago

    Anonymous 

     

    Thanks again for your response but I'm afraid I cannot mirror DEV to look like PROD :( 

    Nevertheless, before coming here for help I tried something like you said, but I couldn't publish the report with PROD's connection string (from DEV) due to connection and validation errors that prompted as soon as PBI Desktop tried to validate the existing schema.

    Also, I couldn't find a way to modify the published report connection string inside the service.

     

    Maybe I did something wrong but I couldn't achieve any of these. Could it be cause I'm employing a Direct Query connection?

     

    Thanks!

    • Anonymous's avatar
      Anonymous
      Not applicable
      8 years ago

      l2aFa Thanks for the feedback. No, I think it sounds like the solution I suggested won't work because of the validation. Thanks for responding with your testing it out. I'm going to ask around on this one, just because I don't like the result :) I'll respond if I can scrounge up any more detail, but it looks like publish from the Prod environment has to be done, or somehow getting the Service connection to connect the same way so the datasources match look like the only options.

      • l2aFa's avatar
        l2aFa
        Helper I
        8 years ago

        Anonymous 

         

        No problem, glad to provide it :)

         

        I finally resolved it publishing the report from within the production environment and for future developments and maintenance this datasource will be accesed through the Power BI Service data connector like we discussed.

         

        Thanks for your help!