RELATED IDEAS
Creating Fieldsets with generic FieldTypes warning
Please, fill in the below fields to enable the processing of your idea.
Who would benefit? |
Implementation consultants |
What impact would it make? |
Less error prone + saves a lot of potential time |
How should it work? |
See context |
Why is it needed? |
Mistake is easily made, a warning should inform consultant and save a lot of hassle afterwards |
Additional feedback, background or context:
Ticket also reased with ID 67754
Terminology ’Generic fieldtype’ = an fieldtype which has no specific fieldtypes enabled, thus no checkboxes in the ‘Fieldset’ property of an FieldType and the property ‘Exclude from Default View’ is not checked
For every customer, we have an XLS file where we design the datamodel. There we have one sheet with (in rows) all the FieldTypes and (in colums) all the Field Sets. We call this the ‘matrix’; in case there is an X in the matrix between the Field Set and the Field Type, it should be linked. In case we have an X for all the Field Sets, we
We had a task to create three new Fieldsets on an existing datamodel. We navigated to the Control center -> Model -> Field Sets -> button ‘Add Field Set’. There we choose the correct Entity and entered the Field set Id + Name in different languages. In our datamodel matrix, I filtered on the ‘X’ in the new Fieldset and then begin searching for the Field Type name in the ‘Excluded fields’ in inriver. One by one, I dragged and dropped them to the ‘Included fields’ and then Saved the creation of the Field Set.
Now this way of working is basically how it should be done I guess. BUT, the thing is that this way of working is creating an unique link between Field Types and Field Sets for the Generic fieldtypes. The result of my changes were that all Generic field types are not generic anymore. They were only linked to the three newly created Field Sets ☹.
I should have filtered the Generic Field Types out in the matrix, but I didn’t.
Where I think inriver could try to help is to show a dialog on the drag-and-drop action. In case you drag a Field Type that is generic (‘Exclude from Default View’ is not checked) and drop it in the left pane, that dialog should warn the person that by doing this there is an impact. As a consultant, you then are warned of the impact and have to confirm that you want to do this.
