I have a View in the Appian Cloud database with a column that concatenates some values, lets call it column "CODES".
I started in our dev environments creating a CDT from Table/View and verifying the datastore.
I then did a distribution to the test environment of the CDT, View and Datastore. While verifying in test environment I get an error that CODES is not a MEDIUMTEXT, it's a LONGTEXT. Not knowing what to do I try to create the CDT in test environment and actually the generated CDT in this environment is different that the one that was generated in dev, even though the database view is the same.
Any suggestions on how to solve this issue? The thing is that I don't know in a production environment which datatype Appian will choose, and I don't want to create objects manually in production, I shouldn't even be able to.
Thank you!
Discussion posts and replies are publicly visible
Did you check the source table's column data type is MEDIUMTEX or LONGTEXT in test environment? If the tables are identical between all environments the view will be of identical structure too.
This is what I see when trying to update the CDT:
wrong column type encountered in column [ABI] in table [`XXXXXX`]; found [longtext (Types#LONGVARCHAR)], but expecting [mediumtext (Types#VARCHAR)]
This is what i see in MariaDB/PhpMyAdmin:
I don't know where Appian is getting longtext/longvarchar from.
Can you post that PhpMyAdmin structure from both environments?
Stefan do you mean the code that generates the View or just the resulting structure? In any case, they appear exactly the same in PhpMyAdmin:
DEV ENVIRONMENT:
TEST ENVIRONMENT:
When I import you can see it recognizes "longtext"
Are you sure they are long text in both environnements?
How do you mean Mathieu Drouin ? As you can see the Database shows one thing, but then Appian shows another and I cannot reconcile the two