Hi All
Made a massive custom file and it will not create the table because it is too big!
Error code is:
ERROR 1118 (42000) at line 1852:
Row size too large (> 8126). Changing some columns to TEXT or
BLOB may help. In current row format, BLOB prefix of 0 bytes is stored inline.There appear to be a few SQL solutions floating around, but I am a bit sceptical of implementing them without considering the impact on Suite.
Princeps
Maybe you should question your original idea of putting massive amounts of data into the database as rows on SuiteCRM records.
Aren’t you better off linking a Note with Attachment to a record? That way the file would be in the file system, it can be as big as you want.
Also, if you’re using a large number of columns in a table, that’s usually a sure sign of bad database design - you should be finding what all those fields have in common, making a table for that abstraction, and then linking records as related records.
If you tell me a bit more about your requirements I can try giving more specific help.
Hi pgr
I am hoping to increase the productivity and reduce double entry by turning a large paper document my company currently uses that takes down all client details into a fields that can be filled in by third parties (via a person form) and finished by staff members.
The problem is staff are against a CRM as they put in the all data already into 5 different systems, (from a paper forms) so I thought. Suite CRM can take client details and staff can fill it in using iPads and computers. I was hoping then to have it create a PDF template of the workflow that replicates the current end form when it is completed.
The details are then filled in across SuiteCRM using workflow, creating appropriate tasks. So the staff have less work overall using the CRM and clients can fill in the details directly.
The form is a real pig, it has to be done over 250 fields for 2 different contacts from 1 account. I made a custom module just for 1 contact and it is too large for the SQL database. I still need to add the second contact fields.
Using a Note with attachment would not work as then I lose the person form functionality and essentially any benefit of having the details captured across the system.
I have considered using 5 different custom modules linked together with each element, but not sure how to tie them together.
Princeps
When you have 250 fields for a record, you REALLY need to review your database design. Just because it was like that on paper, doesn’t mean it should be like that in a relational database.
Those 250 fields are not completely different from one another, are they? You can probably quickly identify that some groups are repetitive, right? These should be in related tables with one-to-many relationships.
This probably is enough to explain your previous difficulties when trying to computerize your processes. If information is not well stored, it is not easy and practical to access, and people abandon the solutions.
Hi pgr
No, the 250+ fields is the cut down form (the paper form before was a single printed sheet monster!) and all of them are a legal requirement for the company to have filled in. they also change per client per interaction.
Is there any plugin or program that you know of that could handle that kind of SQL form that would communicate it effectively into the Suite?
Would be a massive time saver to have it written in once for obvious reasons rather than cherry picking the same data throughout.
I could just attach the written form the to system but that continues the issue instead of addressing it.
Princeps
Well, from now on it’s database design. I can’t help you without knowing what this data is about or how it is structured. But breaking it down into separate related modules is the way to go, it likely will avoid tons of repetition, and all the mistakes that are associated with repetition.