Overview
Snowflake is an analytic data warehouse that is fast, easy to use, and pliable. We have built the Snowflake Connected system to employ these benefits in Appian. You can use this connected system to create an integration object that can help perform SELECT, INSERT, UPDATE, DELETE, CALL FUNCTION or STORED PROCEDURE operations in the Snowflake Database tables or views.
To establish the connection, while creating a connected system you will need
Key Features & Functionality
Hello I am receiving this error can you help check? our current version is 3.0.5 and working with our dev environment but in uat env there are errors please see below:
Error Occurred
JDBC driver encountered communication error. Message: Exception encountered for HTTP request: Certificate for <datavault-ubp_uat.privatelink.snowflakecomputing.com> doesn't match any of the subject alternative names: [*.appiancloud.com, appiancloud.com]. net.snowflake.client.jdbc.SnowflakeSQLException: JDBC driver encountered communication error. Message: Exception encountered for HTTP request: Certificate for <datavault-ubp_uat.privatelink.snowflakecomputing.com> doesn't match any of the subject alternative names: [*.appiancloud.com, appiancloud.com]. in query SELECT * FROM ITRS_WEEKLY WHERE ((ACTIVE_FLAG = 'Y')) FETCH NEXT 1000 ROWS ONLY
Hello would like to ask how you resolved this issue, currently having the same with our env
Hi Mr. Agda
Thanks for reaching out!
We were unable to reproduce the issue. Could you please share the table schema you tried to retrieve?
Hi carlosc0012
Hi admira,
Hi Mr. Agda. I still have a problem with plugin version 3.1.0 on Appian version 24.2. If I understood correctly, you solved the problem with version 3.1.0? Can you please share your experience what you did? Thank you very much.
Hi, we are also seeing the same issue with the upgrade of 24.2.. is it working for anyone with this version?
Hello, I still have the same problem mentioned down with new Appian version
Hi MohammedWasim
Confirming that the updated plugin worked on my personal environment, but on our dev environment it encountered this error
confirming that the issue is no longer encountered. Thank you team