The documentation suggests there are no limitations when setting up party relationship types:
https://learn.microsoft.com/en-us/dynamics365/finance/accounts-receivable/location-relationship
However, some relationship types are not supported and will result in unexpected errors. I consider this a bug, but PG team claims this is an (undocumented) feature, see support case 2412191420001753.
Ideally this bug should be fixed, alternatively the behaviour should be documented in the documentation (which essentially comes down to documenting the bug as a feature).
Comments
We can’t use “Any to Organization “in an entity that is person as the verification for the party, any in this case can be used for person or organization and the other part will be used for organization which is conflicting with the logic of the relation to include the entity that you create the relation on in one of the party of the organizationAnd it goes the other way around if you are trying to use a relation that is “Any to Person “within organization entity you will face the same conflict.This is for verification as the entity type that you will create the relation for needs to be included in the relation type that you will be using.To avoid that you would need to use “Any to Any” in the relation and only then you will be able to use the same relation ID in both organization and person types. A change in the logic needs to be in place for Any to Organization to occupy person and vice versa.
Category: General
I agree, either we need a fix or at least an amend to the documentation, we will collaborate on this with our stakeholders
Category: General