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

error message #3

Closed
kvonachen opened this issue Aug 20, 2013 · 1 comment
Closed

error message #3

kvonachen opened this issue Aug 20, 2013 · 1 comment

Comments

@kvonachen
Copy link

I got the following error message when trying to create a new Opportunity after installing your Apex tool and adding 3 new lookups (opportunity rollup to Contact field).

Error: Invalid Data.
Review all error messages below to correct your data.
Apex trigger dlrs_OpportunityTrigger caused an unexpected exception, contact your administrator: dlrs_OpportunityTrigger: execution of AfterInsert caused by: System.QueryException: unexpected token: 'Date': (dlrs)

Please help!

@kvonachen
Copy link
Author

Nevermind! It was an issue with one of my filters, not your trigger!!

afawcett pushed a commit that referenced this issue Mar 20, 2016
afawcett pushed a commit that referenced this issue Jun 12, 2016
This is actually redundant since the sharing object model is public
read/write for these objects. And as per this issue,
#3
31, can cause install issues, so has now been removed.
afawcett pushed a commit that referenced this issue Jun 18, 2016
afawcett pushed a commit that referenced this issue Jun 18, 2016
afawcett pushed a commit that referenced this issue Jun 21, 2016
afawcett pushed a commit that referenced this issue Aug 14, 2016
#3
45
- Currently i am manually testing MDT scenarios, need to figure out a
test framework for MDT mode!
afawcett pushed a commit that referenced this issue Aug 14, 2016
afawcett pushed a commit that referenced this issue Aug 14, 2016
afawcett pushed a commit that referenced this issue Jan 1, 2017
Upgraded ApexMocks and Apex Commons to latest. Which includes an
entirely new way to check for multi-currency. One which “hopefully”
will avoid the issue described in issue 360. See issue comments for
more.
#3
60
afawcett pushed a commit that referenced this issue Jan 9, 2017
afawcett pushed a commit that referenced this issue May 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant