Fix issue where alert object triggers/notifications attribute was overwritten by the client for the respective attribute #43
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…rwritten by the client for the respective attribute
|
Thanks for the contribution! Before we can merge this, we need @rdas1212 to sign the Salesforce.com Contributor License Agreement. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
_triggers&_notificationsattribute is reserved for the list of triggers and notifications respectively. But in the_fillmethod of the alert service client, these attributes are overwritten by the client object for those services instead of the list of objects to create. Which means that if anAlertobject was created with triggers & notifications defined, those are not usable afterwards.This fix resolves the name conflict by putting the clients in their own attribute.