Search Issue Tracker

Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.




Found in




Issue ID




Parent and child nested Scriptable Object Assets switch places when parent Scriptable Object Asset is renamed

Project Browser


How to reproduce:
1. Download and open the attached project ""
2. Create a parent Scriptable Object Asset (Right-click -> Create -> MyObjects -> ParentObject)
3. Add a child Scriptable Object Asset (MyMenu -> AddChildObject)
4. Rename the NewParentObject Asset

Expected result: NewParentObject Asset is renamed
Actual result: NewParentObject Asset switches places with the NewChildObject Asset and the NewChildObject Asset is renamed

Reproducible with: 2019.3.0a1, 2019.3.0b6, 2020.1.0a8
Not reproducible with: 2017.4.32f1, 2018.4.11f1, 2019.2.8f1

  1. Response avatar

    Resolution Note:

    Requires a system rewrite of how we handle main object name. This is considered a feature. Once it is complete, most bugs in regards to asset names should be fixed. This issue is tracked internally.

Comments (13)

  1. Eb2be104bb042b0bd83d309c4bb3b7c6?d=mm


    Aug 11, 2020 10:20!/;area=summary;u=341770;u=4039!/;area=summary;u=341718!/!/!/!/

  2. 41e194bc6932baeaeb2e633c28d0830a?d=mm


    Jul 28, 2020 10:08;u=245304;u=19154;u=556429;;u=245305;;u=19155;u=556432;;u=556433;u=245302;;u=556434,,,,

  3. 4710745378bd5a7c3aec154a408ef3c4?d=mm


    Jul 12, 2020 20:35

    Here is a workaround for this issue if anyone is interested:

    Basically the issue is caused when the main asset's name is different from the file name.

  4. 3b8554690ef78f027d1be1e442d81394?d=mm


    Jun 10, 2020 09:12

    This issue still exists in 2019.4.0f1

    As ZEEJFPS noted, one workaround is ensure that alphabetic order of the parent < alphabetic order of the children

  5. 690dd33162f4b442491b979ebed4d53e?d=mm


    May 25, 2020 10:29

    Something interesting to note - the file id of the main asset is always (as far as I have seen) 11400000. In the meta file there is a field called mainObjectFileID - which is always 0. Setting this to 11400000 after the swap has occurred reverts the issue. It is really interesting that the main object is easily identifiable in the asset file but still gets lost.

  6. 76b1f86726c7970d7466648c8ae02076?d=mm


    May 18, 2020 10:49

    "This is considered a feature". Yeah that's definitely not a bug from a users perspective. Just as you would expect renaming a file works.

  7. Ad582f21c8594ee6751607a007c27cc8?d=mm


    Apr 08, 2020 13:48

    you can just reset name override from code

  8. A6dca519389585504071fc701b44fc92?d=mm


    Apr 06, 2020 16:46

    Sounds like a great idea Evgeny

  9. 4710745378bd5a7c3aec154a408ef3c4?d=mm


    Apr 05, 2020 18:57

    alphabetically AFTER one of the SubAssets*

    Since I can't edit my comment for some reason.

  10. 4710745378bd5a7c3aec154a408ef3c4?d=mm


    Apr 05, 2020 18:56

    To me it seems like the issue has something to do with how the assets are ordered based on the asset names. This bug only happens if the MainAsset is renamed to something that comes alphabetically before one of the SubAssets. Moreover, this only seems to happen only on the second time the MainAsset is renamed. (In my testing)

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.