Topic by Geraud Andreux
Dear All,
We've hit the limit mentioned in Answer 5626 because we had too many custom fields on the incidents table.
As per (what I understood from) the recommendation in Answer 5626, I've tried to add other custom fields in a new object/table, called "Incidents2" in my case, with the intention to link this table as a child to the main Incidents table.
So far the "Incidents2" table is built, has a few fields, a couple of rows of data. It has a dedicated workspace, and is in my profile and navset. It is a child of the incidents table, based on Incident_ID. When in the new workspace I can indeed pick an existing incident, and then fill values in the new table.
What I'm not able to do however, is to go to the main incidents workspace, and insert fields from the Incidents2 table there. The incidents 2 table is simply not available in the insert fields box.
I can see another custom table there, which I added before (although in an aggregation relationship).
Is it right to think that since the incident ID is the relationship between the two tables, I should be able to simply drag-and-drop fields from the Incidents2 table in the workspace? Or do I need an extra step?
(I've also reset my local data cache and even cleaned all my local install files.)
Thanks for any advice or pointer!
best regards,
Géraud