Skip to main content
To homepage To homepage
Solved

Error when deploying tabular model - "This row has been removed"

T
Visitor

Hi all,

When deploying our tabular model/endpoint (Azure Analysis Services), we get a strange error: "This row has been removed from a table and does not have any data. BeginEdit() will allow creation of new data in this row".

In the error message we don't see which table or row this relates to and we don't know if this error relates to a datawarehouse table or a repository table. All our datawarehouse tables in this tabular model contain data and 'look good'. In addition, this error occurs in one of our environments and not in the other environments. 

Has anyone experience with this error? Any thought on how we can debug this one?

Thanks.

Best answer by Thomas Lind

Hi Rogier
You are most likely correct in thinking that.

Last Thursday we released a new hot-fix with a fix of the perspectives. You would experience that exact error message if you deleted a field that was present in a perspective.

11029: Deleted semantic fields don't remove all related semantic perspective items
Fixed an issue where deleting a semantic field that is used in a perspective did not get remove from the perspective
https://legacysupport.timextender.com/hc/en-us/articles/360051186931 

View original
    Did this topic help you find an answer to your question?

    6 replies

    tld
    Contributor
    Forum|alt.badge.img+1
    • tld
    • Contributor
    • 13 replies
    • March 26, 2021

    Hi Thomas,

    Unfortunately, TimeXtender does not always return the complete error-message to you. However, if you try to do a Process Full on the Tabular model in SSMS, you will get the full error message. 

    Best regards,

    Thomas Duun, Atlytix

    Thomas Duun, Atlytix - https://www.linkedin.com/in/thomasduun/
    rogier.helmus
    Problem Solver
    Forum|alt.badge.img+1
    • rogier.helmus
    • Problem Solver
    • 30 replies
    • August 19, 2021

    Hi Thomas,

    I've run into the same error when trying to deploy a semantic model. Before that I was playing around with semantic model perspectives. I removed those and after that the deployment of the semantic model ran without an issue, so I assume the cause might be in the direction of the semantic model perspectives.

     

    Thomas Lind
    Community Manager
    Forum|alt.badge.img+5
    • Thomas Lind
    • Community Manager
    • 1017 replies
    • Answer
    • August 19, 2021

    Hi Rogier
    You are most likely correct in thinking that.

    Last Thursday we released a new hot-fix with a fix of the perspectives. You would experience that exact error message if you deleted a field that was present in a perspective.

    11029: Deleted semantic fields don't remove all related semantic perspective items
    Fixed an issue where deleting a semantic field that is used in a perspective did not get remove from the perspective
    https://legacysupport.timextender.com/hc/en-us/articles/360051186931 

    anders.e.jonsson
    Contributor
    Forum|alt.badge.img+1

    Hi,

    I get the same error when deploying a semantic model in version 6143.
    I had one perspective which I don’t think affected this model, but I deleted it anyway. Still the same error.

    Since I can’t deploy, there is nothing to process i SSAS.

    Any other suggestions?

    BR

    Anders

    Anders
    Thomas Lind
    Community Manager
    Forum|alt.badge.img+5
    • Thomas Lind
    • Community Manager
    • 1017 replies
    • March 10, 2023

    Hi Anders

    The error is also in the 6143 version. We have made a bug fix for it. It should be fixed in the next release.

    The only way to delete a field from a table in a semantic model, when using perspectives, is to remove it from the perspective first.

    anders.e.jonsson
    1 person likes this
    • anders.e.jonsson
      anders.e.jonsson
    anders.e.jonsson
    Contributor
    Forum|alt.badge.img+1

    Thanks Thomas,

    I just rolled back to a previous version in the SSL and removed the perspective. Then it was just a matter of syncing the SSL.
    Very convenient to be able to go back to a previous version in a single instance.

    BR

    Anders

    Anders

    Reply


    Most helpful members this week

    Terms and ConditionsCookie settings

    Cookie policy

    We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

     
    Cookie settings