You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I commented out the protected $encryptable name and I now get this
Which is the phone number and I can see why this is encrypted because it is personal data, so I think we just need to add migrations to have the database columns accept encrypted strings. Let me know if I have the right approach
This is a problem when migrations are run before the encrypt db fields config is set as true.
There is a migration that checks if field encrption is true, and then alters the data types on these fields to allow for the longer strings.
eg organisation name will be varchar(1000) rather than varchar(255)
I will need to think about how to manage this, prompting a database update required if the setting is changed post running migrations will be a solution
So I created 4 migrations
Each updates the column type from string to text.
crm_organisations - name
crm_phones - number
crm_emails - address
crm_address - line1, line2, line3, city, state, code, country
The organization name is being encrypted and causing a name too long error
The text was updated successfully, but these errors were encountered: