Symfony 2.8升级至3.4：实体ID数组无法保存问题

Hey there! I've dealt with exactly this kind of issue when upgrading Symfony projects from 2.8 to 3.x, so let's break down what's happening and how to fix it.

The Root Cause #

In Symfony 2.8, the form component was more lenient about handling entity associations—when you just called $builder->add('habits') for a collection/association field, it would implicitly handle array-based submissions like your AJAX payload. But starting in Symfony 3.0, the form system requires explicit type declarations for association fields. It won't auto-infer how to process arrays of entity IDs anymore.

Solution 1: Use EntityType with multiple=true (Simplest for Your AJAX Payload) #

Since your AJAX request is sending an array of existing entity IDs (like habits[]: 5), the easiest fix is to use EntityType directly with the multiple option enabled. This tells Symfony to accept an array of IDs and map them to the associated entities.

Here's how to update your AnamnesisType:

use Symfony\Bridge\Doctrine\Form\Type\EntityType;
use Symfony\Component\Form\AbstractType;
use Symfony\Component\Form\FormBuilderInterface;

class AnamnesisType extends AbstractType
{
    public function buildForm(FormBuilderInterface $builder, array $options)
    {
        $builder
            ->add('habits', EntityType::class, [
                // Replace with your actual Habit entity class
                'class' => 'MyHealthBundle:Habit',
                // Choose a field from your Habit entity to use as a label (optional for AJAX)
                'choice_label' => 'name',
                // Allow selecting multiple entities (matches your array payload)
                'multiple' => true,
                // Keep this false since you're submitting IDs via AJAX, not checkboxes/radios
                'expanded' => false,
                'required' => false,
            ])
            ->add('diseases', EntityType::class, [
                'class' => 'MyHealthBundle:Disease',
                'choice_label' => 'name',
                'multiple' => true,
                'expanded' => false,
                'required' => false,
            ])
            ->add('allergies', EntityType::class, [
                'class' => 'MyHealthBundle:Allergy',
                'choice_label' => 'name',
                'multiple' => true,
                'expanded' => false,
                'required' => false,
            ])
            // Add your other fields here
        ;
    }

    // ... rest of your type class
}

Solution 2: Use CollectionType (If You Need Dynamic Entity Management) #

If you ever need to dynamically add/remove individual entity fields in the frontend (beyond just submitting existing IDs), use CollectionType nested with EntityType. This is more flexible but a bit more setup:

use Symfony\Component\Form\Extension\Core\Type\CollectionType;
use Symfony\Bridge\Doctrine\Form\Type\EntityType;

// Inside buildForm()
$builder
    ->add('habits', CollectionType::class, [
        'entry_type' => EntityType::class,
        'entry_options' => [
            'class' => 'MyHealthBundle:Habit',
            'choice_label' => 'name',
        ],
        // Allow adding new entries
        'allow_add' => true,
        // Allow removing entries
        'allow_delete' => true,
        // Critical for updating many-to-many associations (prevents Symfony from skipping add/remove methods)
        'by_reference' => false,
        'required' => false,
    ])
    // Repeat for diseases, allergies, etc.
;

Critical Follow-Up Checks #

1. Ensure Your Entity Has Proper Association Methods
   For Symfony to correctly update the associations, your Anamnesis entity needs add* and remove* methods for each collection. Example for habits:

   // src/MyHealthBundle/Entity/Anamnesis.php
   public function addHabit(\MyHealthBundle\Entity\Habit $habit): self
   {
       if (!$this->habits->contains($habit)) {
           $this->habits[] = $habit;
           // If this is a bidirectional association, uncomment the line below
           // $habit->addAnamnesis($this);
       }
   
       return $this;
   }
   
   public function removeHabit(\MyHealthBundle\Entity\Habit $habit): self
   {
       if ($this->habits->contains($habit)) {
           $this->habits->removeElement($habit);
           // If bidirectional, uncomment this too
           // $habit->removeAnamnesis($this);
       }
   
       return $this;
   }
   

2. Handle AJAX Submission Correctly in Your Controller
   Make sure you're properly parsing the AJAX payload and binding it to the form. If you're sending JSON, you'll need to decode it first:

   // In your controller action
   use Symfony\Component\HttpFoundation\JsonResponse;
   use Symfony\Component\HttpFoundation\Request;
   
   public function submitAnamnesisAction(Request $request)
   {
       $anamnesis = new \MyHealthBundle\Entity\Anamnesis();
       // Or fetch an existing entity: $anamnesis = $this->getDoctrine()->getRepository(Anamnesis::class)->find($id);
   
       $form = $this->createForm(\MyHealthBundle\Form\AnamnesisType::class, $anamnesis);
   
       if ($request->isXmlHttpRequest()) {
           // Decode JSON payload if your AJAX sends data as JSON
           $data = json_decode($request->getContent(), true);
           $form->submit($data);
   
           if ($form->isValid()) {
               $em = $this->getDoctrine()->getManager();
               $em->persist($anamnesis);
               $em->flush();
   
               return new JsonResponse(['success' => true]);
           }
   
           // Return validation errors if the form is invalid
           return new JsonResponse([
               'errors' => $this->getFormErrors($form)
           ], 400);
       }
   
       // Handle non-AJAX requests if needed
       return new JsonResponse(['error' => 'Invalid request'], 400);
   }
   
   // Helper method to get form errors as an array
   private function getFormErrors(\Symfony\Component\Form\FormInterface $form): array
   {
       $errors = [];
       foreach ($form->getErrors() as $error) {
           $errors[] = $error->getMessage();
       }
       foreach ($form->all() as $childForm) {
           if ($childForm instanceof \Symfony\Component\Form\FormInterface) {
               if ($childErrors = $this->getFormErrors($childForm)) {
                   $errors[$childForm->getName()] = $childErrors;
               }
           }
       }
       return $errors;
   }
   

Why This Works #

Symfony 3.4 requires explicit type hints for form fields to avoid ambiguity. By specifying either EntityType(multiple=true) or CollectionType, you're telling the form component exactly how to process the array of IDs from your AJAX request, which aligns with how Symfony 3.x handles form submissions.

内容的提问来源于stack exchange，提问作者Pablo Hessualdo