Skip to content

Latest commit

 

History

History
57 lines (38 loc) · 3.46 KB

File metadata and controls

57 lines (38 loc) · 3.46 KB
  1. Missing Pipelines or Data

After you deploy the solution and open Synapse Studio, you notice that there are no pipelines or data. You might also see a notification that "Publishing in workspace mode is disabled".

image

Resolution - Missing Pipelines or Data

Not all artifacts can be deployed if you don't have Synapse registered in your GitHub account. You need to disconnect and reconnect GitHub from your Synapse workspace to force registration. Once that is complete you will need to redploy the solution.

First you need to switch from Synapse Live mode to GitHub. image

Next you need to head to the Manage Hub and select GitHub Configuration in the navigation pane. image

Now you need to disconnect your workspace from your GitHub account. image

Once you have successfully disconnected GitHub from your workspace it should look like this. image

Now that you have disconnected, it's time to reconnect so the Synapse libraries can be properly installed in your GitHub account. Hit the configure button and select GitHub as your repository type. image

Enter your GitHub repository Owner Name and select Continue

image

Now you will get a pop-up asking to authorize Azure Synapse to your GitHub account. Select Authorize Azure Synapse image

Next you need to grab the URL for your repository to finish the configuration. You can get this by clicking the <>Code button toward the top of your repository and then selecting the Local tab. Now you can just click the copy button next to your HTTPS URL. image

Now go back to your repository configuration and make sure you have the following things set and hit Apply when done:

  • "Use Repository Link" should be selected
  • Paste your URL in the Git Repository Link field
  • Use "main" for the Collaboration Branch field
  • Choose a Publish Branch like workspace_publish
  • You MUST set the Root Folder field to /artifacts including the slash that precedes it

  • The Import Existing Resources field MUST BE UNCHECKED

image

If you get an error about not having permissions to import the repository you need to UNCHECK the import setting. image