Thanks - I was able to get to the problematic field - tags from the acts-as-taggable-on gem - and disable it so we can use everything properly.
In order to help see if this type of field can be fixed, I have shared info below.
the rails schema for the associated tables are
create_table "taggings", id: :serial, force: :cascade do |t|
t.integer "tag_id"
t.integer "taggable_id"
t.string "taggable_type", limit: 255
t.integer "tagger_id"
t.string "tagger_type", limit: 255
t.string "context", limit: 128
t.datetime "created_at"
t.index ["tag_id", "taggable_id", "taggable_type", "context", "tagger_id", "tagger_type"], name: "taggings_idx", unique: true
t.index ["taggable_id", "taggable_type", "context"], name: "index_taggings_on_taggable_id_and_taggable_type_and_context"
end
create_table "tags", id: :serial, force: :cascade do |t|
t.string "name", limit: 255
t.integer "taggings_count", default: 0
t.index ["name"], name: "index_tags_on_name", unique: true
end
The json schema for every model is as follows
{
"field": "tags",
"type": "String",
"default_value": null,
"enums": null,
"integration": null,
"is_filterable": false,
"is_read_only": false,
"is_required": false,
"is_sortable": true,
"is_virtual": false,
"reference": null,
"inverse_of": null,
"relationship": "HasMany",
"widget": null,
"validations": []
}
