#dominoforever | Product Ideas Portal

 

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Repeatable field groups in forms

This idea is mainly targeted for standard notes form development but should also apply to any web development.

Say you want to add multiple addresses on a document. Each address is made up of multiple fields. It would be nice if you could just define a group of fields and add them to a field group array.

Right now you would have to define a preset amount of addresses with separate fields and have to copy default values, validation code etc across each field. It would be nice to add as many addresses you like without repeating code (violating DRY principle). Just have an add new address button and go.

I don't know how this would play out with storing it in the document or displaying in views. I'm thinking computed field names (a separate idea) or parent field reference? and some category-like feature in views.

Having this feature you could possibly nest field groups and end up with a more json-like document.

  • Guest
  • Jun 16 2019
  • Under Consideration
  • Attach files
  • Guest commented
    20 Jun, 2019 12:29am

    I'll leave the implementation details to them but I envision you would do it the same way you would in web development. You can do this easily with XPages and the repeat control but of course you have to compute the field names. Designer should have a new option: Create -> Field group.... You would be given a container with a user definable heading (or no heading if desired). Then give the field group a name (e.g. Addresses). In the container you add fields (Street, City, State, Country, etc). At the bottom of the container you have a button for adding (text/color definable). Clicking on it adds a new section within the container. Then within each new section that gets added you have a button (text/color definable) for removing that section and associated fields within that group. Also definable would be the minimum / maximum (up to unlimited) number of groups and initial number of groups. Then if you want to reference a particular field within a particular group you just give do it like Addresses[4].City. Seems simple enough in theory anyway.

  • Guest commented
    19 Jun, 2019 09:42am

    I see where you are going with this, and I like it.

    I just don’t see how it could work for the user. How does he ‘add’ and address, how would he ‘remove’ one?