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

Duplicate Field Selected error message #155

Closed
Henzell opened this issue Apr 11, 2015 · 5 comments
Closed

Duplicate Field Selected error message #155

Henzell opened this issue Apr 11, 2015 · 5 comments
Labels

Comments

@Henzell
Copy link

Henzell commented Apr 11, 2015

I receive this error when I save a child record.
Apex trigger dlrs_Financial_Coaching_SessionTrigger caused an unexpected exception, contact your administrator: dlrs_Financial_Coaching_SessionTrigger: execution of AfterUpdate caused by: System.QueryException: duplicate field selected: Confidence_Obtain_Your_Credit_Report__c: (dlrs)

My use case is that I am rolling up from a Session record (child) to a Master record (parent). The field that I am aggregating, Confidence_Obtain_Your_Credit_Report__c, is used in 2 rollup summaries. One rolls up using the First aggregate function, with aggregate result field being field A on the parent. The other rolls up the same field, but uses the Last aggregate function, with aggregate result field being field B on the parent.

The error occurs when I have both rollups in Realtime calculation mode. If one rollup is in Realtime and the other is in Scheduled mode, then the error message does not appear.

@afawcett
Copy link
Collaborator

Ok this sounds like a bug, can you include a screenshot of both your rollups please?

@Henzell
Copy link
Author

Henzell commented Apr 15, 2015

Screenshots attached. I'm hoping I can get around the issue by having one rollup work in Realtime, and the other Scheduled.
dlrs 1 2015-04-14
dlrs 2 2015-04-14

@afawcett
Copy link
Collaborator

Ok this is a bug, i'll mark it as such. Sorry about this.

@afawcett
Copy link
Collaborator

afawcett commented Jul 6, 2015

I have now fixed this in the GitHub master branch, and will be releasing in a new managed package for install shortly.

@afawcett
Copy link
Collaborator

afawcett commented Jul 6, 2015

Fixed in v1.21 release.

@afawcett afawcett closed this as completed Jul 6, 2015
@afawcett afawcett removed the priority label Jul 6, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants