Skip to main content
julienc
julienc
January 5, 2023
Question

Synchronized Records Limitation to ORACLE VARCHAR2

  • January 5, 2023
  • 3 replies
  • 0 views

My app is built on an Oracle Database.

Would it be possible to overcome the 4000 byte of Text limitation we have for Synchronized Records fields?

I know the VARCHAR2(4000) limitation is considered to be a standard column type by Oracle, then choosing the EXTENDED for param. max_string_size in the DB would make it an "extended data type", as CLOB is. But since CLOB is forbidden to become a Snyc. RT field, would my large VARCHAR2 columns be also forbidden?

Asking for people who tried it. If no one did, I will ask the DBA, but could be easier to ask here ;)

3 replies

A
ahmada344
August 10, 2023

Hello Julienc,

we have a similar use case at the moment, I'm curious as to what solution you ended up using.

Thank you.

mathieud0001
mathieud0001
Brainy
August 10, 2023

Not possible with synced records. You can set the underlying field to whatever you want but Appian will only synchronize 4000 characters The rest will be truncated.

[View:https://docs.appian.com/suite/help/23.2/records-data-sync.html#exceeding-the-field-character-limit]

Only workaround for fields longer than 4000 is to use the Data Store with CDTs approach.

stefanhelzle0001
stefanhelzle0001
Brainy
August 10, 2023

In that case, you cannot sync that record.

Or, you sync it, but need to do an extra query to fetch these long text fields when displaying the data. Not convenient and troublesome on the long run, but might be worth considering.

Terms & ConditionsAccessibility statement