Entity extend via migration doesn't work properly

Hello,

I tried to add the field head_office into the entity Organization with this migration:

PHP

namespace AppOro\Bundle\OrganizationBundle\Migrations\Schema\v1_0; class AppOroOrganizationBundle implements Migration, ExtendExtensionAwareInterface { /* @var $extendExtension ExtendExtension */ protected $extendExtension; /** * @inheritdoc */ public function setExtendExtension(ExtendExtension $extendExtension) { $this->extendExtension = $extendExtension; } /** * @inheritdoc * @throws \Doctrine\DBAL\Schema\SchemaException */ public function up(Schema $schema, QueryBag $queries) { $table = $schema->getTable('oro_organization'); $this->extendExtension->addManyToOneRelation( $schema, $table, // owning side table 'head_office', // owning side field name 'oro_address', // target side table 'label', // column name is used to show related entity ['extend' => [ 'owner' => ExtendScope::OWNER_CUSTOM, 'cascade' => ["persist", "remove"]] ] ); } }

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36

namespace AppOro\Bundle\OrganizationBundle\Migrations\Schema\v1_0;   class AppOroOrganizationBundle implements Migration, ExtendExtensionAwareInterface {     /* @var $extendExtension ExtendExtension */     protected $extendExtension;       /**      * @inheritdoc      */     public function setExtendExtension(ExtendExtension $extendExtension)     {         $this->extendExtension = $extendExtension;     }       /**      * @inheritdoc      * @throws \Doctrine\DBAL\Schema\SchemaException      */     public function up(Schema $schema, QueryBag $queries)     {         $table = $schema->getTable('oro_organization');           $this->extendExtension->addManyToOneRelation(             $schema,             $table, // owning side table             'head_office', // owning side field name             'oro_address', // target side table             'label', // column name is used to show related entity             ['extend' => [                 'owner' => ExtendScope::OWNER_CUSTOM,                 'cascade' => ["persist", "remove"]]             ]         );     } }

When i perform the command php app/console cache:clear -vvv, i get this error:
Property Oro\Bundle\OrganizationBundle\Entity\Organization::$head_office does not exist

And the file in the cache doesn’t implement new value:

PHP

<?php namespace Extend\Entity; abstract class EX_OroOrganizationBundle_Organization implements \Oro\Bundle\EntityExtendBundle\Entity\ExtendEntityInterface { protected $serialized_data; public function setSerializedData($value) { $this->serialized_data = $value; return $this; } public function getSerializedData() { return $this->serialized_data; } public function __construct() { } }

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22

<?php   namespace Extend\Entity;   abstract class EX_OroOrganizationBundle_Organization implements \Oro\Bundle\EntityExtendBundle\Entity\ExtendEntityInterface {     protected $serialized_data;       public function setSerializedData($value)     {         $this->serialized_data = $value; return $this;     }       public function getSerializedData()     {         return $this->serialized_data;     }       public function __construct()     {     } }

I have another entity that extends Oro\Bundle\OrganizationBundle\Model\ExtendOrganization and having some relation fields.

I am on Oro V2.6.

Thank.

• This topic was modified 3 years ago by  Takushi. Reason: Oro version

Topic

[Yevhen ShyshkinParticipant]

Hello Takushi.

To create new extended field you have to run you migration. Recommended way – execute oro:platform:update command. https://oroinc.com/orocrm/doc/2.6/dev-guide/cookbook/how-to-upgrade-to-new-version

As for another entity extended from Oro\Bundle\OrganizationBundle\Model\ExtendOrganization – it’s not recommended as each extended entity has to have it’s own extended classes. Otherwise application simply will not be able to create correct class aliases for extented entities.

[TakushiParticipant]

Thanks for your response.

My problem is solved by removing the ExtendOrganization on other entity.

What is the recommended way to make this entity same as Organization (with the same properties, relation, etc..) ?
Do i have to duplicate entire Organization entity with his migrations ?

Thank.

[Yevhen ShyshkinParticipant]

The easiest solution is indeed just make a copy of the original organization entity, call it e.g. AdvancedOrganization and then create separate extended model class called ExtendAdvancedOrganization – this way you will have your own independent organization and independent extended entity for it.

Pay attention that in this case new organization entity will not inherit built in organization related features like ACL, ownership etc.

But before that you may stop for a moment and think a little about two absolutely identical entities in your application (which looks like violation of SOLID). Maybe you can add extended boolean flag (e.g. isAdvanced) to the standard Organization entity and distinguish them in this way? Or set some organization as a special organization in the System Configuration and then use this reference to identify it? Or your custom organization logic can be emulated using standard Business Units?

[TakushiParticipant]

Thank you Yevhen Shyshkin !

I mark the topic as resolved.

[Author]

Replies