#Integration62 discussing
- Recent Activity
- Created Date
- Recommended
- All Questions
- Questions with an Accepted Answer
- Unanswered Questions
- Questions with No Accepted Answer
3 answers
The reason for this is because Salesforce stores the Date in UTC time. I assume, when you load your data, the actual UTC datetime of the date you are loading is 1 day earlier.
Since your field is just a date field, any date you provide, is the 12 AM representation of the date, because that's the first time the date is born. For example, 2nd January is born 1 minute after 11.59 PM of 1st January.
Therefore, if your date field is saying 2nd January. Salesforce assume it is 2nd January 12 AM, which when converted to UTC (the format date is saved at the backend), will be 1st January....since, at 2nd January 12 AM GMT+1, UTC is at 1 January 11 PM.
Hi,
Is there a way to upgrade legacy connector to up-to-date external connector? When I try to modify credentials from username-password to key and secret I'm getting "The connector handler specified,Legacy,is unsupported for SalesforceExternal". I have multiple connectors with multiple objects settings so I want to avoid manual configuration as it will takes weeks to finish.
Thanks
1 answer
Greetings@SF CoE
I am assuming this is in CRM Analytics, the good news is we can likely update the underlying metadata via API or deployment tools to avoid rebuilding everything manually.
To help nail down the exact steps, could you check a few quick details?
1. Connector Type: What is the exact connector/adapter name listed in CRM Analytics (e.g., Salesforce External, Redshift, Snowflake, etc.)?
2. Data Sync Status: Are these connectors currently linked to active Data Sync schedules that we can briefly pause during the update?
3. Deployment Preference: Would you prefer updating this via the CRM Analytics REST API or by retrieving and editing the connection definition files in VS Code / Salesforce CLI?
Please answer the questions and I w provide the next steps.
Be well - Katende
Hi All - Good Evening/ Afternoon based on your location I am learning Integration and in my early days
I am using HTTP Post Method to insert record using workbench Please have a look at my code below.
Now we have two custom objects called Hiring Manager and Position, we are trying to add records in our child object i.e., Position Object.
catch here is that I am trying to insert values in our Request body in JSON format, so that record get inserted in our
platform which is salesforce but when i want to enter field Hiring Manager in JSON format records will get inserted only when we provide 18 digits of charater as it's Master / LookUp Field value.
But My requirement here is i should only pass Name of Hiring Manager while creating position record how can we acheive this, your help, thoughts and suggests are highly appreciated.
Apex Class Code:
@RestResource(URLMapping = '/InsertPos/*')Global class MyPositionPostMethod{ @HttpPost Global static string InsertPositionMethod(String PName, String pCurrentstatus, String HrName, String HrPhone, String HrEmail, String HrContact, String posLocation, Decimal MaxBudget, Date mileDate, Decimal MiniPay) { Position__c posRec = New Position__c(); posRec.Name = PName; posRec.Current_Status__c = pCurrentstatus; posRec.Hiring_Manager__c = HrName; posRec.HR_Contact_Number__c = HrPhone; posRec.HR_Email_Address__c = HrEmail; posRec.HR_Contact_Number__c = HrContact; posRec.Location__c = posLocation; posRec.Maximum_Budget__c = MaxBudget; PosRec.MileStone_Date__c = mileDate; PosRec.Minimum_Pay__c = MiniPay; insert posRec; if(posRec.Id != null) return 'Position Record inserted with ID.: '+ posRec.Id; else return 'Position Record failed to insert'; }}JSON Format which is working:
{ "PName": "system", "pCurrentstatus": "Active", "HrName":"a02dM00000ehD1NQAU", "HrPhone": "987458152", "HrEmail": "vivek.Json@gmail.com", "HrContact": "968745120", "posLocation" : "Hyderabad", "MaxBudget": 5000.00, "mileDate":"2026-07-24", "MiniPay": 5000 }
#Integration
3 answers
Since
Lookup/Master-Detail fields store the Salesforce record Id, you cannot directly pass the Hiring Manager's name. Instead, pass a unique field such as the Email Address in the request body, query the Hiring_Manager__c record using that email, retrieve its Id, and map it to the lookup field before inserting the Position record.
Hi everyone,
We're migrating our Salesforce–SharePoint integration from Azure ACS and SharePoint REST APIs to Microsoft Entra ID certificate-based authentication with Microsoft Graph APIs
.
Has anyone implemented this migration? If so, did you encounter any issues, limitations, or unexpected challenges—particularly around certificate-based authentication, Sites.Selected permissions, or Microsoft Graph APIs?
I'd appreciate hearing about any lessons learned or best practices
.
Thanks!
I had Amazon connect Customer integration with salesforce dev sandbox and it worked fine. Then with the same instance I started the configuration to move everything to UAT. But the Sign In CPP after clicking on the phone utility icon; I am unable to loggedin or able to see the login popup.
1 answer
Hi Aisha,
Since the same Amazon Connect instance works in your Dev Sandbox but the CCP login popup doesn't appear in UAT
, the issue is most likely related to the UAT configuration rather than the CTI Adapter itself.
Here are a few things to verify:
- Ensure the Salesforce UAT domain is added to the Approved Origins/Application Integration settings in your Amazon Connect instance.
- Verify that the Amazon Connect CCP URL configured in the Salesforce Contact Center matches your UAT environment.
- Confirm that the Open CTI Softphone Layout and Call Center are assigned correctly to your UAT users.
- Check that pop-ups are allowed for both the Salesforce and Amazon Connect domains, as browser settings can block the CCP login window.
- Verify that the Amazon Connect user has the appropriate security profile and permissions to access the CCP.
- Open the browser's Developer Tools (Console and Network tabs) and check for JavaScript errors, blocked requests, or CSP (Content Security Policy) violations.
- If you're using My Domain, ensure the UAT Salesforce domain has been added as an approved origin in Amazon Connect.
I would like to establish a private connection between Salesforce and AWS EC2 using the PrivateConnect feature. Is there a Salesforce environment where I can try out the PrivateConnect feature for free?
6 answers
First off, thank you to this amazing platform for enabling us to ask questions and share ideas — it's incredibly valuable!
We’re currently implementing a brand new WhatsApp integration via Digital Engagement, and I was hoping to gather some best practices from those who’ve done this before.
Specifically, I have a few questions:
- Meta Business Account setup Is it best to register aMeta Business Account under the client’s business entity rather than using a personal Meta account? - I think this is a "No brainer - Yes"
- Phone number strategy Is it a good practice to:
- Use one phone number for the Production setup, and
- Get a separate number linked to the same Meta Business Account for the Dev/Sandbox environment to support development and testing? I believe we should not test using the Number that is in use for day-to-day business purpose.
- General setup advice What are some “must-do” items or best practices when setting up WhatsApp for Salesforce?
Any recommendations, advice and suggestions would be of great help.
4 answers
These are some common mistakes to avoid when trying to configure Whatsapp in Salesforce.
- Launching before templates are approved.
- Not storing opt-in and opt-out data in Salesforce.
- Letting inbound messages sit in an unowned inbox.
- Creating duplicate Leads for known Contacts.
- Building automation without stop conditions.
- Not testing phone-number formatting and country codes.
- Ignoring reporting until after users complain.
- Using WhatsApp for sensitive content without policy review.
- Training only admins and not end users.
Also you can find some best practices on this link below,
https://www.watbox.ai/blog/whatsapp-salesforce-setup-best-practices/Feel free to reach me if need any queries.
5 answers
If you're already using Amazon Connect with Salesforce, the IVR is typically configured on the Amazon Connect side, while Salesforce is used for screen pops, call routing, and record association. The setup usually involves configuring contact flows, routing profiles, queues, and then mapping the relevant data into Salesforce.
If you're exploring different ways to handle IVR and telephony within Salesforce, you could also take a look at 360 CTI. It supports Salesforce telephony features like IVR, automatic call logging, click-to-dial, and screen pops. Sharing the AppExchange listing in case it's useful while you're evaluating different options: https://appexchange.salesforce.com/appxListingDetail?listingId=a0N4V00000HEVm1UAH
Are you planning to keep Amazon Connect as your telephony provider, or are you evaluating other CTI solutions as well?
Is it possible to create a process to kick-off on an Account record in one SF org that sends some Account Data but also requires manual input of other data that can then be sent to a second SF Org to create a Lead record?
6 answers
@Stephen Oltorik It can be achieved with validation in the flow. When user click on the button, fetch the data from the record which is required to send and see if those fields are blank then display an error message and stop the flow. Similarly make those manually entered data fields as required in the screen flow so the flow display error message when these fields are blank.