I have a one-2-many relationship defined between table a and table b.
Table a shows up once (offcourse) and table b shows up between 3 and more times.
So far so good.
The thing that makes it difficult is that I want to show the content of table b in different forms since I use different fields on different records… I hope you are still with me…
Next to that it is also possible that I show two or more records with the same fields used.
Can look like this
table a - basic form
table b - view a - fields a,b - record 1
table b - view b - fields c,d - record 2
table b - view b - fields c,d - record 3
table b - view c - fields e,f - record 4
table b - view d - fields g,h - record 5
table b - view d - fields g,h - record 6
table b - view d - fields g,h - record 7
For your first issue: how about using a find to search for existing values?
For your second issue: use an event onrecordload to determine which fields you want to hide and/or show
This won’t work since I want to show all the related records wit their different used fields at once…
I made a listview already and did exactly what you suggest with onRecordSelect.
Only when the record is selected (logical) the appropriate fields are shown but… These fields ‘pop up’ for all records.
In other words: When I have a listview and change the visible property of a field that change applies to all the records in the listview. Makes sense but this is not what I want.
onShow won’t make this work either.
I now have a workaround with a seperate recordview and a step-through but my customer doesn’t really like this…
I have 6 types of items, these types need different kinds of information/fields but they are all in table 2. The items in table 2 are related to the records in table 1;
There can be zero-many items of the same type;
I want the customer to have one form to fill with content in one view (I say I but read the customer)…
So instead of a list view with all the same editable fields per record on it I need a list view with different editable fields per record on it… Such a schematic view could look like
basic information (table 1)
item type 1 (table 2) field 1,2,3
item type 2 (table 2) field 1,2,3, 4,5,6,7
item type 3 (table 2) field 1,2,3, 8,9,10
item type 3 (table 2) field 1,2,3, 8,9,10
item type 3 (table 2) field 1,2,3, 8,9,10
item type 4 (table 2) field 1,2,3, 7,8,9
item type 4 (table 2) field 1,2,3, 7,8,9
item type 6 (table 2) field 1,2,3, 11,12,13
The minimum would be 3 different records/items per view, the maximum is undefined!
If this is not clear enough I need to scetch the project. I then prefer to do that offline (and maybe in Dutch?)
I still don’t see any reason to no use merge or calculation fields. If a users wants to edit you can throw up a popup or throw in some editing fields using an event.