CiviCRM Community Forums (archive)

Hi !

I'm trying to create an extension which should give the possibility to specify a relationship for a membership type.

That way it should be possible to activate a relationship on contact creation like this :

• new individual with junior membership type => relationship member of ...

or

• new individual with senior membership type => relationship special member of ...

I think that creating an API could be useful but even before being able to display what I get, my DAO gives me nothing in return when using execute_query().

From what I see, the problem comes from the schema structure table which doesn't contain my table.

First of all, am I right to think that creating an API is usefull and secondly, can anyone help me and tell me which files need to be modified to make it work properly ?

By the way the table I want to add contains just 3 column : id, membership_id, relationship_id. Works just like the _UF_ tables

thank's folks !

Hi,

On 4.3, it needs some hacking to add an api on a new extension and use the generic basis functions.

Have you considered using custom fields rather than a specific custom entity?

Otherwise, not sure I understand the aim of your extension, what's the benefit of a relationship over a membership?

If you start having a lot of members, you'll end up having a lot of relationships, but the interface might not deal too well with that case (eg. the relationship tab doesn't have pagination I think)

X+

We work essentially with health organisations, so we need to create for each member a relation to the correct organisation.

But isn't a membership to the correct organisation already good enough to capture that relation?

It can be made by hand, but what we were asked is this : Create a relationship when a non member pays his contribution and becomes a member.

That is why I think a _UF_ table is better than a custom data.

You lost me: What is this _UF_ table thing is this your custom entity?

X+