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.
Save Microsoft Teams Call Logs to Salesforce
Hi, I've seen a few requests for saving Teams call logs to Salesforce. We built a salesforce managed app to do just that. We are looking for a few beta testers to try the app before we publish it to the AppExchange. UPDATE: Listing is in the AppExchange: https://appexchange.salesforce.com/appxListingDetail?listingId=e4ec0468-7af3-467c-be5e-96dc01503bb5
Bookings-Salesforce Calendar Integration
Good Day, Our ORG has begun rolling out Microsoft Bookings to our internal staff. One key point that was brought to my attention was the integration to Salesforce. I was able to locate some threads were users were posting customer data to salesforce but could not find anything about the calendar integration. Has anyone had any success in when a meeting is booked, this gets relayed over to salesforce via (logic app or powerautomate)
ERROR running force:source:convert: Expected file at path: D:\a\1\s\force-app\main\default
HI All, Thanks in advance for reading my issue. I am trying to deploy the changes to the target Salesforce org. While doing that I am using the below code to deploy. But the below is deploying only the components ending with.cls, but I want all the components to be deployed to target org irrespective whether it is ending with .cls or not. Could someone suggest where i am going wrong? # Powershell script for partial builds echo "Entering Powershell" echo $env:WORKSPACE echo "Cleaning temp directory" #Remove-Item -recurse temp -Force | Out-Null $files = git diff-tree -r --no-commit-id --name-only --diff-filter=ACMRT HEAD~1 HEAD echo $files #Gives the name of file along with its path ,that has been changed, the lastest commit echo "Re-creating temp directory" new-item -Name "temp" -Force -ItemType directory | Out-Null foreach($file in $files) { echo "printing file name" #Replace slash $file = $file -replace "/","\" #Copy files to temp directory echo FA|xcopy $file temp\$file echo $temp #Check extension $extn = [IO.Path]::GetExtension($file) if ($extn -eq ".cls") { $metafile = $file + "-meta.xml" echo FA|xcopy $metafile temp\$metafile echo $temp } } # echo "Copy package.xml" # echo FA|xcopy force-app\package.xml temp\force-app\ echo "Removing force-app" Remove-Item -recurse force-app #create force-app new-item -Name "force-app" -Force -ItemType directory | Out-Null Start-Sleep -s 5 echo "Copying back contents of temp" Copy-Item temp\force-app\* force-app\ -recurse dir force-app -recurse
Can we run Microsoft Healthcare Bot or Bot Framework on Salesforce Marketing Cloud?
Hi All, Scenario is: Client want to develop a digital sales rep/virtual assistant for the Sales representatives. Given the fact that they have Veeva CRM running on Salesforce Marketing Cloud. And having said that they have some interest around MS Bot Framework and Healthcare Bot. Question is: 1. How can we make run MS Bot Framework on this scenarion i.e. Veeva CRM on SFC Marketing Cloud? 2. Do we have any similar reference architecture somewhere to refer to? 3. How this can be possible? May be with node.js code of Bot Framework on Salesforce and then make it connect and derive business logic through Azure Logic Apps Any insights, inputs, reference to architecture and support will be helpful here. Thank you
