Does anyone know why apprian would show that a table has multiple primary keys, when the table only has 1 primary key, 3 foreign keys and an alternate key?
Discussion posts and replies are publicly visible
Could you provide a bit more detail? Are you receiving an error when trying to sync a record? I ran into a similar problem where a record sync was complaining about "multiple primary keys" but it ended up being a schema permissions issue related to the connected system attempting to connect to the DB.
It is when first setting up a record type.
Can you share a screenshot of the "structure" tab for that table within PhpMyAdmin?
Ahhh, I see now it does have 2 primary keys, I was looking at the keys list rather than the structure.
I assume there is no way around being able to use records and not data types with tables that have multiple keys.
Would it be possible to alter the table and set it to only have 1 primary key? I'm unclear what the befit would be for having more than 1 defined. It wouldn't (afaik) affect your ability to have data stored in that second column or anything.
I wish it would, but this is a database/table that is setup and used primarily by are ERP system
For now then you may be correct, in that you might be stuck using the Entity Data setup if you need to directly interact with that table from within Appian.
Additionally though, I'd urge you to open a support case with Appian specifying this use case, so they can get it in their product pipeline to perhaps cook up a way to either handle this case (or at least give developers the option to manually declare a 'main' primary key or some other override) so that you don't have to abandon the RecordType setup. I don't know how soon they might come up with some enhancement to handle that, but it'd be good for them to be aware of real-world use cases that prevent adoption.