Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • seanrock 99 posts 173 karma points
    Jul 09, 2010 @ 23:15
    seanrock
    0

    The DELETE statement conflicted with the REFERENCE constraint "FK_cmsPropertyData_cmsPropertyType".

     

    The DELETE statement conflicted with the REFERENCE constraint "FK_cmsPropertyData_cmsPropertyType". The conflict occurred in database "BenderMachine", table "dbo.cmsPropertyData", column 'propertytypeid'.
    The statement has been terminated.

     

    I created a few properties for a child document type. I later (erroneously) created identical properties (alias) on the parent document type. When i tried to delete the properties from the parent document type i get the above error. I can delete the child properties however even after that i still cannot delete those properties on parent document type. The properties had no value (neither the child or parent doc)

  • seanrock 99 posts 173 karma points
    Jul 09, 2010 @ 23:55
    seanrock
    0

    I had to manually remove the items from cmsPropertyData table and then from the cmsPropertyType table.

  • Sjors Pals 615 posts 268 karma points
    Jul 14, 2010 @ 16:03
    Sjors Pals
    0

    We had the same problem..

  • Sjors Pals 615 posts 268 karma points
    Aug 10, 2010 @ 17:02
    Sjors Pals
    0

    I noticed that this still happens when you try to delete a property on a documenttype that has other inherited doctypes.

  • Sjors Pals 615 posts 268 karma points
    Aug 11, 2010 @ 09:58
    Sjors Pals
    0

    Noticed shortly after i posted this, that this should be fixed 4.5.1 (was running 4.5)

  • Ismail Mayat 4288 posts 9247 karma points MVP 2x admin c-trib
    Aug 11, 2010 @ 17:42
    Ismail Mayat
    0

    Sjors,

    I had this issue in 4.5.1 it stopped by home page from loading in backend. I updated the db so that the constraint relationship cascades on delete. That allowed me to remove properties and my home page came back to life.

    Regards

    Ismail

  • Sjors Pals 615 posts 268 karma points
    Aug 11, 2010 @ 18:00
    Sjors Pals
    0

    Well, it's not really a big issue at the moment, for a client we created a lot of properties to manage real estate objects, we have one "master" real estate object, with properties like city,citypart and neighbourhood, but when we started building the website, we realised that it was easier to create documenttypes for city,citypart and neighbourhood a sitestructure which is equal to those. So i wanted to delete them from the real estate documenttype, which failed..

    I told our client to ignore them, and placed them in the properties tab, but i think it's nice to delete them, if they aren't used.

    We are not upgraded to 4.5.1 yet, since we are gonna launch the site monday, and we do have a stable environment at the moment, and we think it's to riscy to upgrade 2 days before going life.

  • Jeroen Breuer 4860 posts 12121 karma points MVP 3x admin c-trib
    Sep 01, 2010 @ 12:58
    Jeroen Breuer
    0

    I've upgraded from 4.5.0 to 4.5.1, but I still have this exception. Somehow the constraint relationship is not updated. Should I do this manually or is there a better way to fix this?

    Jeroen

  • Ismail Mayat 4288 posts 9247 karma points MVP 2x admin c-trib
    Sep 01, 2010 @ 13:27
    Ismail Mayat
    0

    Jeroen,

    I did it manually cascade on delete and that sorted the problem.

    regards

    ismail

  • Ismail Mayat 4288 posts 9247 karma points MVP 2x admin c-trib
    Sep 01, 2010 @ 13:28
    Ismail Mayat
    0

    Jeroen,

    I did it manually cascade on delete and that sorted the problem.

    regards

    ismail

  • Sjors Pals 615 posts 268 karma points
    Sep 01, 2010 @ 13:47
    Sjors Pals
    0

    Clear, but this means that the issue is still not fixed in 4.5.1 .....

  • Sjors Pals 615 posts 268 karma points
    Sep 01, 2010 @ 13:47
    Sjors Pals
    0

    Really funny, i was just updating the Jira issue about this for a client ;)

  • Jeroen Breuer 4860 posts 12121 karma points MVP 3x admin c-trib
    Sep 01, 2010 @ 14:10
    Jeroen Breuer
    0

    It's probably fixed for a clean umbraco 4.5.1 install, but might go wrong for an upgrade from 4.5.0 to 4.5.1.

    Jeroen

  • Priscilla 1 post 21 karma points
    Sep 07, 2010 @ 16:29
    Priscilla
    0

    We experienced a similar issue with the following key when trying to delete a tab:

    FK_cmsPropertyType_cmsTab

    We used the same method Ismail mentioned which was to add a "cascade" on delete to this key.

  • Rik Helsen 670 posts 873 karma points
    Nov 09, 2010 @ 09:28
    Rik Helsen
    0

    I just ran into the same issue with Umbraco 4.5.2...

    Surlely this is a grave enough bug to deserve some attention!

  • Rik Helsen 670 posts 873 karma points
    Nov 09, 2010 @ 09:37
    Rik Helsen
    0

    How do I clean this up? delete the row from cmsPropertyType or does it require additional actions?

     

     

  • Rik Helsen 670 posts 873 karma points
    Nov 09, 2010 @ 09:44
    Rik Helsen
    1

    This did it for us:

    DECLARE @id int
    SET @id = 89 /* id of the propertytype that you can't delete in the Umbraco backend*/

    DELETE FROM [DataBaseName].[dbo].[cmsPropertyData]
    WHERE [propertytypeid] = @id

    DELETE FROM [DataBaseName].[dbo].[cmsPropertyType]
    WHERE [id] = @id

    Then as a last step manually delete the property from the doctype

  • Rik Helsen 670 posts 873 karma points
    Nov 09, 2010 @ 11:10
    Rik Helsen
    0
  • Anthony Dang 1404 posts 2558 karma points MVP c-trib
    Dec 15, 2010 @ 17:11
    Anthony Dang
    4

    Here is a quick fix that does not involve manually deleting things...
    Open up SQL Management Studio, and change the relationship between cmsPropertyType and cmsPropertyData for delete to "cascade".
    :)

  • Lachlann 323 posts 545 karma points
    Jun 06, 2011 @ 10:31
    Lachlann
    0

    Just ran into this problem in 4.7 and changing the relationship between cmsPropertyType and cmsPropertyData for delete to "cascade", works fine.

     

    L

  • John C Scott 440 posts 1076 karma points
    Dec 19, 2011 @ 13:04
    John C Scott
    0

    just ran into this issue in 4.7

    just to confirm what i will try changing in SQL Server Management Studio

    is this under the table for cmsPropertyType > Constraints or is this somewhere else?

  • John C Scott 440 posts 1076 karma points
    Dec 19, 2011 @ 13:39
    John C Scott
    0

    just ran into this issue in 4.7

    just to confirm what i will try changing in SQL Server Management Studio

    is this under the table for cmsPropertyType > Constraints or is this somewhere else?

  • Sébastien Richer 194 posts 429 karma points
    Jul 10, 2012 @ 17:19
    Sébastien Richer
    0

    Just got this in 4.7.2.

  • John C Scott 440 posts 1076 karma points
    Jul 10, 2012 @ 21:32
    John C Scott
    0

    just to confirm this fix as outlined above did work for me in 4.7.1. and would i think work the same in 4.7.2

  • Sébastien Richer 194 posts 429 karma points
    Jul 10, 2012 @ 21:35
    Sébastien Richer
    0

    Yes I got this with a somewhat weird datatype in my CMS. Adding the on delete cascade delete fixed it and I used another data type.

  • Thomas 65 posts 87 karma points
    Aug 21, 2012 @ 11:24
    Thomas
    0

    I also got it in 4.7.1

    But adding didn't seem to fix the problem - or have I misunderstood something.

  • Sébastien Richer 194 posts 429 karma points
    Aug 21, 2012 @ 15:52
    Sébastien Richer
    0

    Thomas, I think there were two rules that needed to be changed to Cascade. I forgot the other one, but normally you get the information in the error stack trace.

  • Tarik 35 posts 106 karma points
    Sep 06, 2012 @ 19:22
    Tarik
    0

    I fixed the issue by updating the two tables below:

     

  • Thomas 65 posts 87 karma points
    Sep 07, 2012 @ 13:40
    Thomas
    0

    Thanks Nazm - that did the trick!! :o)

Please Sign in or register to post replies

Write your reply to:

Draft