Hello, We have a use case where we use the torecord function to trans

@thanosm Keeping the torecord function (or best practices) aside, 70 shouldn't be a problem. I use a cdt which has 92 fields (of which some of them are nested CDTs) and there are no issues with it.

Any insights on the torecord function? And what do you mean by "best practices" in relation to this function?

@thanosm Sorry, I didn't used this function till date. Best practices in the sense, we faced performance issues when we make queries over the data store entity (that has got 90+ fields) for display purposes, especially on record dashboards. Thereafter, we created one more cdt, corresponding data store entity which maps to the same table in the database, but just consists of frequently used columns and there was a drastic improvement in the performance.

Hope you will gain a better insight in subsequent comments by other Appian practitioners.

The torecord() function expects a second argument which will be a variable of the same target CDT, maybe your PV is of type CDT^1 meaning is a previous version that didn't have the 3 extra fields.