![]() ![]() While I love the Inline Entity Forms module, it lacks the bulk editing features that Views Entity Form Field brings to Views. My first thought was to use the great Paragraphs module, but I finally decided to vote for the Inline Entity Form module to add and edit the referenced products or services to proposals and invoices. I really fancy the way Drupal Commerce uses Inline Entity Forms for editing product variations in the backend of a product entity. Proposals and invoices are simple entities that reference a collection of products or services. The app creates invoices and proposals amongst other things. I recently worked on an app that is used to manage an event location with loads of annual events. They allow users to edit the fields' values right in the View's results: Instead of adding the field outputting the field's value, the Form field is placed on the view. And the module is surprisingly heasy to handle. ![]() The module basically allows users to edit entities right at the results page of a View, instead of having to open each result separatedly to edit it. The primary use case is the parent -> children one (product display -> products, order -> line items, etc.), where the child entities are never managed outside the parent form." "Provides a widget for inline management (creation, modification, removal) of referenced entities. When they see a view displaying multiple entities, they want to be able to edit them all at once, instead of clicking an edit button on each row.Įven though it's still in Beta, I usually end up using Views Entity Form Field(or Editable Views for Drupal 7) to create an "Excel like" workflow. It's project page says about the module: Sometimes when we're creating new tools for customers that were heavily using Excel spreadsheets, they find it hard to get used to the "standard" Drupal workflow.
0 Comments
Leave a Reply. |