Repackage - Salesforce Service cloud to fix UserEmail blank column issue#12896
Merged
Conversation
v-sabiraj
previously approved these changes
Oct 1, 2025
Contributor
v-sabiraj
left a comment
There was a problem hiding this comment.
looks good, waiting for customer to confirm on the changes.
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR updates the Salesforce Service Cloud solution to version 3.0.6, addressing an issue where the UserEmail column was appearing blank due to incorrect field mapping. The fix updates the data transformation logic to map USER_NAME to the UserEmail column instead of USER_EMAIL.
Key Changes
- Corrected the UserEmail column mapping from USER_EMAIL to USER_NAME in the KQL transformation queries
- Added USER_NAME field to the schema definitions to support the corrected mapping
- Updated version references from 3.0.5 to 3.0.6 across all solution files
Reviewed Changes
Copilot reviewed 4 out of 5 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| Solutions/Salesforce Service Cloud/Package/mainTemplate.json | Updated solution version, added USER_NAME schema field, corrected UserEmail mapping in transformKql, and reformatted JSON property ordering |
| Solutions/Salesforce Service Cloud/Package/createUiDefinition.json | Enhanced data connector description to clarify it uses Codeless Connector Framework |
| Solutions/Salesforce Service Cloud/Data/Solution_TSalesforceCloudtemplateSpec.json | Incremented solution version to 3.0.6 |
| Solutions/Salesforce Service Cloud/Data Connectors/SalesforceSentinelConnector_CCP/SalesforceServiceCloud_DCR.json | Added USER_NAME schema field and updated transformKql to map USER_NAME to UserEmail |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
v-sabiraj
approved these changes
Oct 17, 2025
v-atulyadav
approved these changes
Oct 17, 2025
This file contains hidden or 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
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.
Required items, please complete
Change(s):
Reason for Change(s):
Version Updated:
Testing Completed: