• Andrew Smith - 6 years ago

    We currently don't have any plans to offer this feature.  As a work around, you can create a new object for the detail and migrate the data either as part of an install script or through a post install operation in your app.

    The problem with allowing this is that existing objects lose their OwnerId field and also their [ObjectName]Share table in the API.  If a customer has built integrations or customized the app to use these fields/objects then the package upgrade will fail.  In addition, certain customizations are not possible on detail objects that are allowed on standalone (lookup) objects.  This again complicates the upgrade.  

    We'll continue to re-evaluate this feature as new capabilities are added to the platform that might permit us to allow this.   
    • Flag

  • Patrick Chetot - 6 years ago

    Definetly needed
    • Flag

  • Rocky Assad - 7 years ago

    This would be the best. 
    • Flag

  • Sam Mercado Ostolaza - 7 years ago

    This is needed.
    • Flag

  • Manu Dewan - 7 years ago

    Just ran into the situation where we REALLY need this!
    • Flag

  • Daniel Chang - 7 years ago

    This feature can def help our organization as well
    • Flag

  • Shayne O'Sullivan - 7 years ago

    Agreed - roll up fields would be great from managed objects!
    • Flag

  • Emily Jensen - 8 years ago

    We could definitely use this.
    • Flag

  • Dev One - 8 years ago

    Much needed feature...
    • Flag

  • Chris Marantette - 8 years ago

    This would be a very useful tool and much needed!
    • Flag

  • Jason Hartfield - 8 years ago

    Yes - we are now having to make the decision to build a whole new object and do a data migration to the new object or do all the calculations in triggers instead.
    • Flag

  • Fixed Assets Dev - 9 years ago

    We could use this feature
    • Flag

  • Haridinesh Ketepalli - 9 years ago

    Yes,
    This is usefull and sholud enable this feature.
    • Flag