I know you say the feedback is extensive but its not helped me.
The previous topics cover extensively what causes this issue and ways to fix it. It is almost always caused either by having far too many fields or database isn't configured correctly. In theory you should be able to have 1000 fields before hitting the limit, but that's excessive.
It's not their job but they are going to try and look into it for me.
If it's a database configuration issue it will be something they'll likely need to adjust.
They wish to know, what is the name of table CB uses to store the fields. That way they can look at the table.
Fields are stored as new columns on the _comprofiler table where CB user rows are stored.
As so many have come up with this issue, maybe when you release CB 3, this problem may be more forgiving?
It won't be an issue ever again in a future release as we'll be moving fields off the _comprofiler table and instead into a separate table entirely, but that won't happen until we rewrite our core APIs which won't be done until CB 3.x. We maybe able to get this change in sooner than that, but at this time I can't say for sure. We planned to begin this process beginning of this year, but pandemic has set us back significantly as we've had to shift priorities.
krileon
