Not sure if this belongs in #ideas-features or not, but probably, given how it turned out after I wrote it.
So, it’s clear that one of Fibery’s greatest strengths is in its ability to replace multiple systems, bring data from various places into one location and interconnect it, etc. But the more I do that (now with Discourse and Airtable connected, and plans to add more), the more “type proliferation” I have. And the thing that is most challenging with this is that in many cases there are overlapping intents for some component of the data, most often it is the “contact”/“user” Type. While this may be by far the most common case, I’m sure there are other examples.
So I’m wondering if there is a general solution to avoiding having a bunch of types that all store and represent similar or overlapping data. Obviously the email address is often shared, and you can auto-match on that to connect Entities together. But that doesn’t solve the “Type Proliferation”, and is also far less convenient than seeing all data in a single view, on a single Type. We don’t have a way of moving Fields between Types, and even if we did that would probably break the syncing, which I’d very likely want to avoid. What I’d really love is the option to just pick an existing Type and setup syncing of a single “type” (e.g. Contacts, Companies, etc.) from an external tool into the existing Type in Fibery.
In comparison in a system like Airtable I can import a CSV, match on Email, and “update” or “enrich” the existing rows/entities/values/fields with the new data (and create any missing entities as well). Of course I recognize things are different in Fibery, and it has its own CSV import as well. But the integration functionality has so much value, I think the kind of capability I’m describing is really needed. Anyone else have similar concerns/needs? Is there an existing way to even partly address this that I’m missing? (besides just linking the same “kind” of Type together via rules)