Hello, guys and thank you for such great module.

Currently we develop our ERP system and one part of it based on CRM Core. So it means that we also inherit your entities.

The problem we faced is that your activity entity has a set of pre-defined fields that being added to an activity bundle every time when we create a new one. But in our system we don't need some of pre-defined fields, and we would love to have possibility to alter the fields and field instances before new activity bundle is created. Of cource, we could do it later, but it doesn't seems like a proper Drupal-way (first create field, then immideately delete it). Also this alter would be very useful for addinig our own fields and field instances.

Patch with proposed solution is attached.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

RoSk0’s picture

Version: 7.x-0.9 » 7.x-1.x-dev
Status: Needs review » Needs work

I don't see any reasons we should not add this.
The only this is that you also should add documentation to this patch. Documentation should be placed here crm_core.api.php.

Thanks!

Spleshka’s picture

Great, but maybe it makes sense to add this documentation to crm_core_activities.api.php?

RoSk0’s picture

No. We want to keep all documentation in one place.

Spleshka’s picture

Added documentation.

Anonymous’s picture

Status: Needs review » Reviewed & tested by the community

Looking at this carefully, will likely include it in the new release of CRM Core.

Spleshka’s picture

I would very appreciate this, thanks!

  • Commit a402343 on 7.x-0.x by techsoldaten:
    Issue #2216295 by Spleshka: making activity fields optional
    
Anonymous’s picture

Status: Reviewed & tested by the community » Closed (fixed)

  • Commit a402343 on 7.x-0.x, import by techsoldaten:
    Issue #2216295 by Spleshka: making activity fields optional
    

  • Commit a402343 on 7.x-0.x, import, activity_pages by techsoldaten:
    Issue #2216295 by Spleshka: making activity fields optional