Access announces removal of Salesforce ODBC driver in October 2025
MS Access 2019 (and newer) ships a licensed Salesforce ODBC driver from InsightSoftware that will lose sustaining support after June 30th, 2026. But because we can no longer provide updates for the driver, the Access team has decided to accelerate the removal of this driver and remove it from the product in October 2025. Applies to: Access 2019 volume licensed and Enterprise plans Access 2021, Access 2024, and Microsoft 365 subscriptions Access 2021 and Access 2024 as part of the Office 2021 and Office 2024 perpetual licenses (standalone versions) The Salesforce ODBC driver bundled with Office includes shared libraries such as: libcurl.dll libcrypto-3.dll libssl-3.dll These libraries are located under the following path: Program Files\Microsoft Office\ODBC Drivers\Salesforce. They may also be present in different locations. Drivers installed by Office and used to access your Salesforce data will be removed on permanently on October 28, if you are using Access as part of a Microsoft 365 Apps monthly version and on November 11 if you are on the semi-annual release. For customers using perpetual Access 2019, 2021, or 2024, the drivers will be removed on November 11. You do not need to manually remove the drivers. Access currently doesn't have a way to talk directly to the Salesforce APIs so customers must continue to use the standardized ODBC driver framework that we currently support. Customers can independently purchase the Simba.DLL driver if needed from InsightSoftware. There are also other vendors that offer a Salesforce driver. Simba driver from InsightsSoftware https://insightsoftware.com/simba/ ODBC driver from devart https://www.devart.com/odbc/salesforce/ Salesforce integration from boomi https://boomi.com/solutions/application/salesforce/ Salesforce driver from cdata https://www.cdata.com/drivers/salesforce Once you purchase and install the driver, Access can connect to your Salesforce external data source. On the External Data ribbon, choose New Data Source > From Other Sources > ODBC Database We will provide more updates when available.
Copilot for Sales required field error on custom object
I am getting the following error when trying to create a custom object record in copilot for sales. There’s a new required field in this form, and your Copilot for Sales admin will have to update the settings to match before you can save this here. Send these error details to your admin, and ask them to match the required fields in Copilot for Sales to the ones in [Dynamics 365/Salesforce], then try again. The two required fields are already added. The only other field required is the contact field and that is greyed out in the teams settings. If is a rather siple object so not sure what is the problem.
To Surface the Custom Object Data From Salesforce In Copilot For Sales Side Panel
There is a Key Sales Info Card in Copilot For Sales on connecting to Salesforce CRM it fetches Opportunity, account and contact info in it . I need to display a custom object which is linked to contact and it's associated account in the key sales info . Is there any Process or do we have any workaround to build it in a separate card. Refere the image belowMeeting Prep Card
Enabled the required permissions as outlined in the referenced article. https://learn.microsoft.com/en-us/microsoft-sales-copilot/meeting-prep Scheduled a meeting with a contact. Logged the meeting in Salesforce using Copilot for Sales. Expected Result: Since the meeting was scheduled an hour in advance, a Meeting Prep Card was expected to appear in the Copilot chat before 40-70 min of call start. Can anyone suggest me issue with the functionality.
Salesforce CRM - connector and trial env issues
We've deployed Copilot for Sales following the steps in the deployment guide https://learn.microsoft.com/en-us/microsoft-sales-copilot/deploy-viva-sales-sf for a customer but they're unable to sign in. Issue 1: the Microsoft Power Platform connector is not showing up in Salesforce CRM under 'Connected apps' or 'Connected apps OAuth usage'. Salesforce support is of no help and keep pointing to Microsoft for this, even though I suspect that this should be a default connector that should be visible in the Salesforce Environment? Issue 2: When they open outlook and try to sign in through copilot for sales, the sign in keeps loading without showing an error on the front-end. When we open up the console on the page, the below error shows: The trial environment creation is blocked. Step 7 of the deployment guide says that any user can trigger the creation of the msdyn_viva environent and the tenant creation restriction is bypassed: We've gone ahead and enabled the setting trial environment creation for all users in the power platform admin center anyway but this does not solve the issue. worth mentioning: Both users that tried to sign in have the Copilot for Sales license Both users are Salesforce CRM admins. They have plenty of dataverse database storage available to create a new environment any help would be greatly appreciated.Facing an issue while forwarding the Email to Salesforce Email Services
I am trying to forward an email from Outlook to a Salesforce Email address. It works fine when forwarding to an personal email address, but it does not seem to be work when forward to Salesforce. I am using redirect rules to forward the email. Below is the Salesforce email for reference: email address removed for privacy reasons
Salesforce agent copilot chat window - how to implement?
check out this "agent copilot" chat window inside of salesforce: i got this screenshot from our Microsoft sme - but in turn i have yet to receive any step-by-step on how to enable this in our salesforce cloud or if this agent copilot chat window is even possible? as there is no Microsoft article i can find describing this. even talked to the SME that gave the screenshot and all she sent was article on how to setup copilot sales in outlook and teams. so i ask this community - have you seen this salesforce copilot chat window and how do you implement this??
