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

thanosm over 10 years ago

Hello,

We have a use case where we use the torecord function to transform an XML to a specific CDT. The problem is that the last 3 fields of the CDT do not contain the values of the respective elements in the XML.

The CDT contains approximately 70 fields.

Is there a limit to the number of fields that can be processed in a CDT within the torecord function? Is there generally some limit to the number of fields that a CDT should have?

Regards.

Discussion posts and replies are publicly visible

Parents

0 sikhivahans over 10 years ago

@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.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 sikhivahans over 10 years ago

@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.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data