We are using data-sync records and allowing Appian to automatically generate the tables. We ran into an issue where the maximum row length of 65535 bytes is being reached in MariaDB so we are unable to add any more columns. The issue here is that Appian defaults text fields to varchar 255 and "long text" to 4000. Therefore, if you have 16 long texts in a record type, you're already at the row limit. Further, there is no way to change the text length in the Record Type Designer. Changing a field length on the DB side require us to go back into the Record Type Designer and re-map the field since the data type has changed. Consequently, we need to also remap all references to the record field, which is a tedious task.
1. Will Appian enable an easier way to change text lengths in Record Type designer without needing to run a SQL script, remap the field, and repoint all field references?
2. Does Data Sync support the TEXT data type instead of VARCHAR? I believe TEXT data type will not count against the row limit in MariaDB.
Discussion posts and replies are publicly visible
I don't think that Appian will change that as long as the 4000 chars limit for text fields in synced records stays.
But your case is a good example for the limitations of any low-code approach. BTW, Appian allows you to review the DDL code it creates for the tables. You can then adapt it to your specific needs.
And yes, changing these things later in the development cycle is not exactly painless.
1. Yeah, I'd say this is one of downsides of working with Record Types vs Data Types. Hopefully they will address this in a future release.
2. Doubt they will ever allow TEXT data types for sync.