updating .sqlproj file (version issue with git)

Hi justfetz​ ,

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?

Regards
Chaithanya

The CI patch looks like it’s solving a different problem. Check .platform/config.version first. When System update available appears, commit the pending changes, apply the update, then commit the Warehouse from the workspace to Git.

Export alone won’t update the repo .sqlproj. Since you’ve already tried both update paths, could you share the exact sync error and the Git versions from .platform and .sqlproj?

Hi justfetz​ ,

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?

Regards
Chaithanya

Hi justfetz​ 

We ran into the same issue when we needed to update the SQL solution file in order to get some queries to work the way we want to, we are using YAML pipelines to build and deploy the solution, our pipeline failed on the build validation of the SQL solution of our queries, that was why we were looking to update. 
We had the same issue that the update was oke for a second, but reverted and showed a change back to the old version in the workspace

Our solution was to, set the build version during our build so we could validate the SQLproj file, i have included our solution from our build pipeline. Hopefully this helps you with your issue.

Did I answer your question, please mark the post as a solution.

  - name: sqlProjSdkVersion   
    value: '2.2.0'
    # Build-only override. Fabric's git integration regenerates the
    # <Sdk Name="Microsoft.Build.Sql" Version="..."/> line in the .sqlproj
    # on every Commit from the workspace, so it must never be edited in git
    # (it will just show up as a revert diff in the Fabric portal). Pin the
    # version the CI build actually needs here instead, and patch it only into
    # this pipeline's disposable checkout, right before the dotnet build step.


    # Patch the SDK version only in this ephemeral checkout, never committed back.
    # Keeps the file Fabric owns untouched in git while giving the build the SDK
    # version it needs. Regex matches whatever version Fabric last wrote, since that
    # value can change over time as Microsoft updates the backend build packages.
    # Every *.Warehouse folder under folder/ is discovered and built, so adding
    # a new Warehouse to the solution needs no change to this pipeline.
    - script: |
        set -e
        shopt -s nullglob
        FOUND=0
        for SQLPROJ in folder/*.Warehouse/*.sqlproj; do
          FOUND=1
          echo "Pinning SDK version in ${SQLPROJ}"
          sed -i -E "s/(<Sdk Name=\"Microsoft.Build.Sql\" Version=\")[^\"]*(\")/\1$(sqlProjSdkVersion)\2/" "$SQLPROJ"
          # Report the resulting line, but never fail the step on a non-match:
          # under set -e a grep that finds nothing would abort the whole build.
          grep -m1 'Microsoft.Build.Sql' "$SQLPROJ" || echo "  (no Microsoft.Build.Sql SDK line in this project)"
        done
        if [ "$FOUND" -eq 0 ]; then
          echo "##vso[task.logissue type=error]No .sqlproj found under folder/*.Warehouse/"
          exit 1
        fi
      displayName: 'Pin Microsoft.Build.Sql SDK version (build-only, not committed)'