<%= form_with model: @form, scope: :form, url: page_bulk_upload_lettings_resume_path(@bulk_upload, page: "fix-choice"), method: :patch do |f| %> <%= f.govuk_error_summary %> Bulk upload for lettings (<%= @bulk_upload.year_combo %>)

How would you like to fix <%= pluralize(@bulk_upload.bulk_upload_errors.count, "error") %>?

<%= govuk_details(summary_text: "How to choose between fixing errors on the CORE site or in the CSV") do %>

When it comes to fixing errors, there are pros and cons to doing it on a CSV versus doing it on a website.

Fixing errors on a CSV file can be beneficial because it allows you to easily make changes to multiple records at once, and you can use tools like Excel to quickly identify and correct errors. However, if the CSV file is not properly formatted, it can be difficult to identify which records contain errors.

Fixing errors on a website can be convenient because you can see the data in context and make changes in real-time. However, this approach can be time-consuming if you need to make changes to multiple records, and it may be more difficult to identify errors in a large dataset.

Ultimately, the best approach will depend on the specific situation and the nature of the errors that need to be fixed.

<% end %> <%= f.govuk_collection_radio_buttons :choice, @form.options, :id, :name, legend: { hidden: true } %> <%= f.govuk_submit %> <% end %>