#mounirmtl
obtuse quartz
Yeah you'd need to create a new person. Those objects exist on the connect accounts themselves
proper hare
Even if it's the same physical individual?
Interestingly business types that are not individual allows to add/reuse persons on the connected account
obtuse quartz
Can you share an example request id where we allowed you to reuse a person id from another account?
How exactly did you do that?
cinder oarBOT
proper hare
Oh wait, no a person is tied to an account you're right. My bad
You can use multiple persons on an account but you can't use a person on multiple accounts
obtuse quartz
Yeah
proper hare
If it's not too much to ask, May i ask why this design decision and not allow to reuse a person object across accounts?
When a user updates their info, it kinda forces us to go through all the accounts this user is attched to, and update all those persons object with the same info
obtuse quartz
I can't say why, but it's because the person object exists on the account it's created on. All api objects that are created on a particular account aren't accessible from another account
proper hare
I see, the account_id is part of the "primary key" to retrieve any object attached to it, I guess?
obtuse quartz
You can think of it that way
I obviously can't reveal how data is modeled internally though
proper hare
I understand. But I can see why now. It's basically a multi tenancy issue. where 2 accounts are considered 2 different tenants regardless of who owns those accounts in real life
obtuse quartz
Exactly
proper hare
That makes sense. Thanks for the answer