Rails: How to have a nested form save to different nested models?

Question

Context:

I have a Company model that has many projects. Each project has many tasks. The company has many employees.

Employee belongs to Company and has many tasks. It is one employee per task and an employee will have only one task per project.

Schema:

Problem:

I'm building a form to create a project where the user can add multiple tasks. Each task has an amount of hours specified and the employee performing the task. Upon submission the form should create a single project record, one or more task records with hours and employee_id attributes and (!) check if the employee name already exists in the database or create a new one.

I'm struggling with how to have the form save the employee_id rather than the employee_name.

Code:

My form is as follows:

<%= simple_nested_form_for @project do |f| %>
    <%= f.input :project_details %>
    <%= f.simple_fields_for :tasks do |task| %>
        <%= task.input :employee_name, input_html: { data: { autocomplete_source: @queried_employee_names.to_json } } %>
        <%= task.input :hours %>
    <% end %>
    <%= f.link_to_add "Add +", :tasks %>
    <%= f.button :submit %>
<% end %>

My controller:

class TransactionsController < ApplicationController

  def new
    @project = current_company.projects.build
  end

  def create
    @project = current_company.projects.new(project_params)
    if @project.save
        employee_save
        redirect_to success_url
    else
        @project = current_company.projects.build
        render :new
    end
  end


    # save the employees not yet in the database
    def employee_save
      @project.tasks.each do |task|
            if current_company.employees.where(name: task.employee_name).empty?
              current_company.employees.new(name: task.employee_name).save 
            end
        end
    end

  def project_params
    params.require(:project).permit(:project_details, tasks_attributes: [:id, :employee_name, :hours, :_destroy])
  end
end

Question:

Unfortunately, this would save to the tasks table the employee_name rather than employee_id (plus writing a new employee_name to the employees table). Of course, the tasks table should only contain the employee_ids and the employee table the names.

Any suggestions on how to approach this?

Hi if my answer was useful, please consider select it as accepted answer, that's how the community works... — svelandiag
– svelandiag, Commented Mar 2, 2016 at 19:25
Hi SsouLlesS, thanks for the answer and your time. Quite frankly the answer (comment) by j-dexx was most useful here. You mentioned the use of a hidden field, which in the end I did not use. Perhaps if you would summarise the comments mentioned below I will accept. Currently it is not 'the' solution. Cheers, M — Matthias
– Matthias, Commented Mar 2, 2016 at 22:20
Yes I know it was not the full answer, but it may be useful for others looking for this same topic, not because it was not useful only for you means it is not an useful answer. Regards — svelandiag
– svelandiag, Commented Mar 3, 2016 at 0:00

svelandiag · Accepted Answer · 2016-02-17 23:36:14Z

0

I would add a hidden field in the form like:

<%= simple_nested_form_for @project do |f| %>
    <%= f.input :project_details %>
    <%= f.simple_fields_for :tasks do |task| %>
        <%= task.input :employee_name, input_html: { data: { autocomplete_source: @queried_employee_names.to_json } } %>
        <%= task.hidden_field :employee_id, '' %>
        <%= task.input :hours %>
    <% end %>
    <%= f.link_to_add "Add +", :tasks %>
    <%= f.button :submit %>
<% end %>

This field must be filled through Ajax. I see you have an autocomplete source in your :employee_name input field, well you can add an event there when you select the employee, and get the id through Ajax and fill the hidden field with the id of the selected employee, that way you can easily save that data in your create action.

answered Feb 17, 2016 at 23:36

svelandiag

4,3701 gold badge44 silver badges82 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

Matthias Over a year ago

thanks. That indeed sounds like a solution. Do you also have a suggestion how to deal with this on the controller side?

j-dexx Over a year ago

It's an old episode but this would work for you

Matthias Over a year ago

Good suggestion to watch the Railscast. I actually found a more recent one #102 that even better describes this issue. There is one remaining issue however, how to link the new employee record to company this way. I've described this here. Thanks again!

Collectives™ on Stack Overflow

Rails: How to have a nested form save to different nested models?

1 Answer 1

3 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

3 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related