Interacting with Relationship Class Beyond Creation Possible?

Glasnoct

I'm currently trying to wrap my head around relationship classes and there seems to be a dearth of information on interacting with them beyond the ability to create them or describe them. Is reading from/writing to RCs not exposed in the arcpy API? Even in the GUI the RC object doesn't give me any ways to introspect it; I can't open it as a table to see *what* is in it, if anything.

Can I add relationships to it by providing the key pair? Is it an SQLite database like .stylx files are and I'd have to interact with it via the SQL python module? I can find a dozen example on *creating* a relationship class with arcpy but nothing beyond that--even finding the RC in the database in convoluted and only returns the describe object as opposed to the actual RC object itself.

 

If I can't interact with it meaningfully with arcpy, is it exposed in another API I can stumble my way through to modify it?

Glasnoct

I was initially not, no. Which would explain the inability to see any of the relationships. Why attribution is disabled by default when creating a relationship class, I do not know but at the same time I haven't really wrapped my head around all there is to be aware of with relationship classes.

Once I got the RC regenerated as attributed, I was able to get access to the intermediate table. Using a regular InsertCursor seems to have updated the table as a test without complaint, so hopefully that should satisfy my original question.

I am a little perplexed, though. If it were as simple as running the typical cursors on the intermediate table, why was I not finding any discussion about that? I had run into a road-block with programmatically affecting relationship classes at a previous job where there seemed to be no answer outside of possibly doing it through the C# SDK for ArcPro (if I recollect). Maybe the lack of attribution was the cause, as I don't remember being able to access the relationships as easily as opening up an intermediate table of the relationship class. 🤔  Our M.O. at the time was to manually select and create the relationship through the context menu, over and over again, across thousands of features--easily the worst part of our workflow. I did just try this now with a 1:M relationship type; maybe the M:N relationship class was what we were using and may prove to be an issue. Something I'll have to test later...