Forum Discussion

Hamp79's avatar
Hamp79
Frequent Visitor
1 year ago
Solved

Help, please!!.Error to refresh Semantic Model into workspace- "column doesn´t exist"

Hi, I would like to know if anyone might give me a hint about an error I am facing.
Although message error says that there isn´t an specific column when refresh semantic model into a workspace. 

It is actually not true,because,that column does exists, so i dont´know what do next.
Besides when I refresh in power bi desktop i don´t have any issue.

Example:
Data source error: Expression.Error: The column 'TASKUNIQUEID' of the table wasn't found.. TASKUNIQUEID. . The exception was raised by the IDbCommand interface. Table: PROJ_TASK_ADDL.

I look forward your respone or any clue could share with me.

Thanks

  • Hamp79's avatar
    Hamp79
    1 year ago

    Hi, sorry for my delay in reply all of you.
    Actually I guess all responses have been made of my thread might be correct as good practice.
    But really what affect to my issue didn´t work, also because I didn´t mentioned that part of my source came of API web and there is what was the error.

    Finally I found the problem, although i don´t know yet why....Let me explain:

    In power query part  code of API web, i might select where say " columns" and filter with sql code, and filtering columns i want to show... and that worked well in power desktop but when i uploaded to power service gave error of "column didn´t find"

    So solution i found, was removing that part and showing all columns (writting * symbol)
    ----- 
    Paginas = List.Generate(
    () => [offsetPage = 1, pages = 1, Data = {}],
    each [offsetPage] <= [pages],
    each [
    response = Web.Contents(url,
    [
    Headers = [#"Authorization" = "Bearer " & accessToken,
    #"Ocp-Apim-Subscription-Key" = "xxxxx",
    #"columns" = "*",  // don´t work in my API code selecting by specific columns....
    #"offsetPage" = Text.From([offsetPage])
    ]
    ] develeoped:
    ......


    Thanks

10 Replies

  • Hi. If you have checked that the column exists with an external DBMS quering the exact same table/view and the column is right there, the next step is checking the permission for the login account at Service. Column can be hidden for users as a security purpose. If the credentials used for that don't see the columns it will fail even if it really exists.

    If the problem is still there, you will need to open it in query editor power bi desktop and check step by step at which step is failing and why.

    I hope that helps

    • Hamp79's avatar
      Hamp79
      Frequent Visitor

      Thanks, but regretfully two first steps were checked, and nothing. I am feel stuck and lost, because I don´t see anything out of normal in power bi desktop.
      The only error I see is in Service, but when refresh in desktop comes out well.

      • ibarrau's avatar
        ibarrau
        Super User

        Because is not working, there is a difference somewhere. Make sure the credentials edited at Power Bi Service are the same one you are using for refreshing at desktop.

        Regards

  • Hi Hamp79 

    1. Verify Data Source Credentials in Power BI Service
    Go to Power BI Service → Workspace → Dataset Settings → Data source credentials

    Make sure the credentials are valid and have permission to see the column/table.

    2. Check Gateway Settings
    If your source is on-prem, ensure the Gateway is configured properly, and the data source is mapped correctly.

    Go to Power BI Service → Manage Gateways → Verify the source is listed and working.

    3. Check for Column Use in DAX Measures or Visuals
    Even if the column exists in the model, it may not exist in the source table during refresh.


    🌟 I hope this solution helps you unlock your Power BI potential! If you found it helpful, click 'Mark as Solution' to guide others toward the answers they need.
    💡 Love the effort? Drop the kudos! Your appreciation fuels community spirit and innovation.
    🎖 As a proud SuperUser and Microsoft Partner, we’re here to empower your data journey and the Power BI Community at large.
    🔗 Curious to explore more? [Discover here].
    Let’s keep building smarter solutions together!

    • v-aatheeque's avatar
      v-aatheeque
      Community Support

      Hi Hamp79 ,

      we haven't heard back from you regarding our last response and wanted to check if your issue has been resolved.

       If the response addressed by the community member for  your query, please mark it as Accept Answer and click Yes if you found it helpful.

       

      Thank You.

  • Hamp79's avatar
    Hamp79
    Frequent Visitor

    HI, athough all responses might be good and I guess needed, but in my case are not enough. I still have problem. 
    Thanks, i keep working on it.

  • Hi Hamp79 

     

    Try:

    1. Republish the dataset from Power BI Desktop to Power BI Service and refresh again.
    2. Check the data source credentials and access permissions configuration
    3. 
    Verify theData Source settings in Power BI Service
    4. Try clearing cache

     

     

     

    Regards,

    Ritesh

    Community Champion

    Please mark the answer if helpful so that it can help others

    Dance-Sing with Data Projects - YouTube

    • v-aatheeque's avatar
      v-aatheeque
      Community Support

      Hi Hamp79 ,

      If the information is helpful, please accept the answer by clicking the "Upvote" and "Accept Answer" on the post. If you are still facing any issue, please let us know in the comments. We are glad to help you.

       

      We value your feedback, and it will help us to assist others who might have a similar query. Thank you for your contribution in enhancing Microsoft Fabric Community Forum.

      • v-aatheeque's avatar
        v-aatheeque
        Community Support

        Hi Hamp79 ,

        Just checking in to see if you're still experiencing the issue with the missing column during the semantic model refresh. From your earlier message, it sounds like the column does exist and works fine in Power BI Desktop, which suggests the issue might be related to the dataset or schema differences in the service workspace.

        If you’re still facing the problem, feel free to share any recent changes to the model, query structure, or source permissions — we’d be glad to help troubleshoot further.

        If the issue has been resolved, kindly consider marking the helpful response as Accepted to guide others facing a similar scenario.

        Looking forward to your response!