This is an older issue, but still very much present, and becoming more and more an obstacle. I had reported several months ago to @yang regarding issues with column types in integration query windows. At the time, it was with an integration with Airtable, this time is with an integration with a Postgres database.
The issue is with the way Plasmic detects or recognizes data types of the respective api. With Airtable, it wouldn’t recognize certain columns, like Attachment fields. Now with the Postgres DB, it doesn’t recognize fields of type ENUM and JSON (and possibly others), the values of which are simple strings.
For example, in the Postgres DB table I have a “status” field of type ENUM that can be one of three options: “approved,pending,rejected”. So each row in the table will hold one of these. Because Plasmic doesn’t recognize these field types, I am unable to create a query to fetch rows with a certain status, because that field does not appear for selection in the filter’s Add Rule dropdown.
This forces me to write a custom SQL query inside an input field that is too small to type/edit queries in. So the entire experience is very painful, instead of being as simple as three clicks: Click to Add Rule, Click to select field, type in the desired value.
In the Postgres DB, I also have a field of type JSON, which simply holds a JSON object/string. Since the field is not recognized, I cannot “use integrations” that create or update rows, because the fields are missing from the list of fields that can be “filled”, which again forces me to write custom SQL queries for write operations, which frankly I would rather not. Or, it forces me to change my DB field type to string, which would make it visible on the Plasmic side but create other inconveniences in other areas and the other platforms.
This is very limiting and in many ways blocking for me, as I cannot conveniently create forms and interfaces in Plasmic for all the required purposes. So at this time, I am embedding external forms from other platforms instead of building everything out in Plasmic.
A solution for this could be as simple as showing all available fields in integrations windows, regardless of their type, or at least provide an option like “Show unknown fields” in a manner similar to how dynamic value windows have a “Show advanced fields” option.
Can this be finally addressed please so we can actually be able to use the integrations and the data available? (Especially since these are supposed to be official integrations, in the case of Airtable and Postgres.)
Thanks.
