Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CRM-19568 Expose processor ID to views #406

Merged
merged 1 commit into from
Nov 3, 2016

Conversation

konadave
Copy link
Contributor

@konadave konadave commented Oct 26, 2016

@monishdeb
Copy link
Member

@konadave will it be $data['civicrm_contribution_recur']['payment_processor_id'] instead ?

@konadave
Copy link
Contributor Author

konadave commented Nov 3, 2016

@monishdeb No.

processor_id varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL COMMENT 'Possibly needed to store a unique identifier for this recurring payment order - if this is available from the processor??'

@monishdeb
Copy link
Member

Hmm I think you are right, but not sure about the title because apparently 'Processor ID' mean the payment processor's ID used for recurring payment instead of unique identifier.

@konadave
Copy link
Contributor Author

konadave commented Nov 3, 2016

This came about as a request from a client...

"How much time would it take to make the Processor ID field from civicrm_contribution_recur available to Views? This field corresponds to Auth.net's ARB's subscription ID, their unique identifier for recurring payment subscriptions."

The processor ID assigned by the payment processor is a unique identifier.

@monishdeb
Copy link
Member

I see. Tested on my local and it works fine for me. Merging ..

@monishdeb monishdeb merged commit 7d48e47 into civicrm:7.x-master Nov 3, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants