PHP - Tango : Taco Next Generation Objects

Array
(
    [0] => stdClass Object
        (
            [first_name] => test
            [last_name] => test
            [title] => test
            [id] => 34
            [type] => 4
            [manager] => 4
            [email] => p@yahoo.com
            [date] => 2014-09-21 07:23:12
            [status] => 2
            [approval_date] => 2014-09-21 07:31:10
            [assessment_id] => 1
            [supervisor_approval] => 1
            [manager_approval_date] => 2014-09-21 07:31:27
            [mainmanger] => 3
        )

    [1] => stdClass Object
        (
            [first_name] => test
            [last_name] => test
            [title] => test
            [id] => 34
            [type] => 4
            [manager] => 4
            [email] => p@yahoo.com
            [date] => 2014-09-20 07:39:55
            [status] => 2
            [approval_date] => 2014-09-20 07:40:41
            [assessment_id] => 3
            [supervisor_approval] => 1
            [manager_approval_date] => 2014-09-20 07:41:07
            [mainmanger] => 3
        )

    [2] => stdClass Object
        (
            [first_name] => jimmy john john
            [last_name] => john
            [title] => Lorad and Master
            [id] => 32
            [type] => 4
            [manager] => 3
            [email] => j@j.com
            [date] => 2014-09-21 07:38:50
            [status] => 2
            [approval_date] => 2014-09-19 07:39:25
            [assessment_id] => 2
            [supervisor_approval] => 1
            [manager_approval_date] => 2014-09-19 07:39:25
            [mainmanger] => 0
        )

)

Array
(
    [0] => stdClass Object
        (
            [first_name] => test
            [last_name] => test
            [title] => test
            [id] => 34
            [type] => 4
            [manager] => 4
            [email] => piznac@yahoo.com
            [date] => 2014-09-21 07:23:12
            [status] => 2
            [approval_date] => 2014-09-21 07:31:10
            [assessment_id] => 1
            [supervisor_approval] => 1
            [manager_approval_date] => 2014-09-21 07:31:27
            [mainmanger] => 3
        )

    [1] => stdClass Object
        (
            [first_name] => jimmy john john
            [last_name] => john
            [title] => Lorad and Master
            [id] => 32
            [type] => 4
            [manager] => 3
            [email] => j@j.com
            [date] => 2014-09-21 07:38:50
            [status] => 2
            [approval_date] => 2014-09-19 07:39:25
            [assessment_id] => 2
            [supervisor_approval] => 1
            [manager_approval_date] => 2014-09-19 07:39:25
            [mainmanger] => 0
        )

)

I have the following three tables (and also delta_point and hist_point which are purposely left out and just mentioned for context).  Before going down the Doctrine ORM long curvy road, aggrType was just used to restrict possible values so that I didn't need to use MySQL's ENUM, but now I am thinking there may be value to making it an entity and include some methods (and a second reason because I still can't figure out how to make Doctrine create a FK constraint yet not populate the parent entity with a AggrType object).

point
-id (int PK)
-data
-dType /* descriminator.  Options are AggregatePoint, DeltaPoint, and HistoricPoint */

aggr_point
-id (int PK, FK to point)
-aggrType (char FK to aggrType)
-data

aggrType
-type (char PK) /* there are about five types */

I have a service to create a new point based on the provided desired type and user data.  I don't like the switch statement to determine which type of point to create, but don't know a better way.  Also my entity is responsible to provide the appropriate validation rules for the given point type which might not be considered proper but it seems to work for me.  Any constructive criticism is welcomed.

<?php
namespace NotionCommotion\PointMapper\Api\Point;
use NotionCommotion\PointMapper\Domain\Entity\Point;
class PointService
{
    public function create(string $type, array $params):integer {
        $class=[
            'aggr'=>'AggregatePoint',
            'delta'=>'DeltaPoint',
            'hist'=>'HistoricPoint',
        ][$type];
        //$class='Point\\'.$class;  //This doesn't seem to be possible and I needed to use the fully qualifed name without the short cut used namespace.
        $class='\\Greenbean\Datalogger\Domain\Entity\Point\\'.$class;
        $point=new $class();
        $validator=$this->getValidator($point);
        $params=$validator->sanitize($params);
        $validator->validate($params);
        $point->setAccount($this->account);
        $point->populate($params, $this->em); //Will be addressed later
        $this->em->persist($point);
        $this->em->flush();
        $point->setIdPublic($this->em->getRepository(Point\Point::class)->getPublicId($point->getId()));
        return $point->getIdPublic();
    }
}

Now, this is the part I am struggling with the most.  I only have one service to create any type of point, so I do wish to put a bunch of if/thens in it and instead move logic to the individual point type being created.  The AggrPoint in question requires a sub-point and I don't think it is appropriate to inject the entity manager into a point entity and as an alternative solution find an existing point which is associated with the account which resides in the new AggrPoint.  Maybe not appropriate, but it works.  This type of point also has a sub-object AggrType as discussed at the very beginning of this post, so I first attempt to create a new one from scratch, but that doesn't work and I need to set $aggrType with an existing one.  As an alternative, I passed the entity the entity manager, but as stated I think this is a bad idea.

Any recommendations where to go from here?  Thank you

namespace NotionCommotion\PointMapper\Domain\Entity\Point;
class AggregatePoint extends Point
{
    public function populate(array $params, \Doctrine\ORM\EntityManager $em):\NotionCommotion\PointMapper\Domain\Entity\Entity{
        $criteria = \Doctrine\Common\Collections\Criteria::create()
        ->where(\Doctrine\Common\Collections\Criteria::expr()->eq("id_public", $params['pointId']));
        if(!$subpoint = $this->getAccount()->getPoints()->matching($criteria)->current()){
            throw new \Exception("Invalid subpoint ID $params[pointId]");
        }
        $this->setSubpoint($subpoint);

        //This won't work since I must use an existing AggregateType and not create a new one
        $aggrType=new AggregateType();
        $aggrType->setType($params['aggrType']);

        //This just seems wrong and I shouldn't be passing the entity manager to an entity
        $aggrType=$em->getRepository(AggregateType::class)->findOneBy(['type'=>$params['aggrType']]);

        $this->setAggregateType($aggrType);

        unset($params['pointId'], $params['aggrType']);
        // parent::populate($params) not shown, but it basically calles appropriate setters based on the property name
        return parent::populate($params);
    }

    public function getValidatorRules():array
    {
        return $this->filesToArr(['/point/base.json', '/point/aggr.json']);
    }

}