CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Developer Discussion (Moderator: Donald Lobo) »
  • I think CRM-10684, a closed issue, is not fixed (completely). What should I do?
Pages: [1]

Author Topic: I think CRM-10684, a closed issue, is not fixed (completely). What should I do?  (Read 405 times)

johanv

  • I post occasionally
  • **
  • Posts: 65
  • Karma: 5
  • #chiro #geek #linux #beer
    • my homepage
  • CiviCRM version: 4.7.x
  • CMS version: Drupal 7.x
  • MySQL version: 5.x
  • PHP version: 5.x
I think CRM-10684, a closed issue, is not fixed (completely). What should I do?
January 26, 2015, 07:36:14 am
(I updated this post, see 1st comment)

Hi all,

Issue CRM-10684 (Relationship API "get" op doesn't return custom data if custom group extends specific relationship type) is marked as closed on the issue tracker, but I think this problem is not completely fixed.

If I create a custom field that is e.g. only extending the child-of-relationship, and I try to get a child-of-relationship with a value for this field using the API, it does not return the custom value if I explicitely specify the custom field (in my case custom_7) as a field to return.

So I guess this issue might be only partially solved.

What should I do next? Should I open a new issue on the issue tracker? Or is there a way to re-open the old one?

Thank you,
Johan
« Last Edit: January 26, 2015, 11:20:30 am by johanv »

johanv

  • I post occasionally
  • **
  • Posts: 65
  • Karma: 5
  • #chiro #geek #linux #beer
    • my homepage
  • CiviCRM version: 4.7.x
  • CMS version: Drupal 7.x
  • MySQL version: 5.x
  • PHP version: 5.x
Re: I think CRM-10684, a closed issue, is not fixed (completely). What should I do?
January 26, 2015, 09:02:07 am
OK, this partially me being stupid (as usual :)). My API user didn't have the permissions to access the custom fields.

But the problem with the fields to return, is still valid.

JohnFF

  • I post frequently
  • ***
  • Posts: 235
  • Karma: 6
  • CiviCRM version: 4.4.13
  • CMS version: Drupal 7.28
  • MySQL version: 5.5.31-1
  • PHP version: 5.3.27
Re: I think CRM-10684, a closed issue, is not fixed (completely). What should I do?
January 27, 2015, 02:16:51 am
Dear johanv,

If I've understood you right, then you just need to be told that in order to get custom fields that are attached to a specific type, then you have to include that type ID.

For example, if you have custom fields attached to relationship type id 2 then in your API call you must include:

relationship_type_id => 2

Hope that helps!
If you like empowering charities in a free and open way, then you're going to love Civi.

Email Amender: https://civicrm.org/extensions/email-amender
UK Phone Validator: https://civicrm.org/extensions/uk-phone-number-validator
http://civifirst.com
https://twitter.com/civifirst

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Developer Discussion (Moderator: Donald Lobo) »
  • I think CRM-10684, a closed issue, is not fixed (completely). What should I do?

This forum was archived on 2017-11-26.