Project

General

Profile

Actions

Feature #8962

open

allow for form fields with identical names

Added by Nicola Chiapolini over 4 years ago. Updated about 2 months ago.

Status:
New
Priority:
High
Assignee:
Carsten Rose
Target version:
Start date:
29.08.2019
Due date:
% Done:

0%

Estimated time:
Discuss:
Prio Planung:
No
Vote:

Description

We have a form with three Action-Elements all pointing to the same column. Each of them calculates the value based on a different dynamic-update form-field (restricted via requiredList).
This works perfectly, but I need to adjust the name directly in the database...

Could this check be removed? (At least for action elements, but I can imagine this to be useful even with native dynamic-update elements.)

Actions #1

Updated by Carsten Rose over 4 years ago

  • Priority changed from Normal to High
  • Target version set to 146

Das sollte moeglich sein.

Moeglichkeit um das flexibel zu konfigurieren:

  • Neue Konfigurationsoption (Store System): feSameName=allow|forbid|action
    • allow: FE Elemente mit identischem Namen ist ok.
    • forbid: FE Elemente mit identischem Namen sind nicht moeglich (Default).
    • action: FE Elemente mit identischem Namen sind fuer Action Elemente moeglich.
  • Der Check in Form.name='FormElement', FE.label='Check Name Conflict' wird wie folgt angepasst:
    sqlValidate={{!SELECT fe.id FROM FormElement AS fe WHERE "{{class:F:alnumx}}"=fe.class AND fe.formId={{formId:RF}} AND fe.name!="" AND fe.name="{{name:F:alnumx}}" AND fe.id!={{id:R0}} AND ('forbid'='{{feSameName:VY}}' OR ('action'='{{feSameName:VY}}' AND fe.class IN 'native,container')  ) }}
    
  • Mit #8963 (Variablen koennen einfach im V-Store gesetzt werden) kann das dann zusaetzlich auf Form.parameter und FormElement.parameter Ebene gesetzt weden.
Actions #2

Updated by Carsten Rose over 4 years ago

  • Status changed from New to Some day maybe
Actions #3

Updated by Carsten Rose over 4 years ago

  • Status changed from Some day maybe to New
Actions #4

Updated by Carsten Rose about 4 years ago

  • Assignee set to Carsten Rose
Actions #5

Updated by Carsten Rose about 4 years ago

  • Target version changed from 146 to 55
Actions #6

Updated by Carsten Rose about 4 years ago

  • Target version changed from 55 to next7
Actions #7

Updated by Carsten Rose almost 3 years ago

  • Target version changed from next7 to next4
Actions #8

Updated by Carsten Rose over 1 year ago

  • Target version changed from next4 to Check if 'high' is still necessary
Actions #9

Updated by Carsten Rose 7 months ago

  • Target version changed from Check if 'high' is still necessary to 24.8.0
  • Prio Planung set to No
Actions #10

Updated by Carsten Rose about 2 months ago

  • Target version changed from 24.8.0 to 24.3.1
Actions

Also available in: Atom PDF