AIforce and the Permission Cleanup It Just Made Urgent
📍 Part of our Dreamforce 2026 coverage — start with the full announcement recap Your sales team may never open a Lightning page again. 😳 At Dreamforce 2026 Salesforce introduced AIforce, and the login screen quietly stopped being the only front door to your CRM. That is mostly great news. It also means every forgotten permission set in your org is about to get a much louder voice. AIFORCE / PERMISSION EXPOSURE “Show me every renewal above $50K closing this quarter that also has open support cases.” ! Permission set from a 2019 pilot still grants View All on Cases Row 2 includes a case this rep was never supposed to see One plain question, one old permission set, one exposed answer — nobody broke in. What AIforce actually does AIforce is a live interface layer that sits on top of Agentforce, Data 360 and Customer 360. Instead of clicking through tabs and list views, people and agents reach Salesforce data and actions from the tools they already work in, starting with Slack and Claude. Interfaces can be composed by simply describing what you need, so a sales manager no longer waits two sprints for an admin to build a new dashboard. Salesforce designed it with trust at the center. Every request runs on your existing permissions and business rules, each agent sees only what the person asking can see, and every action routes back through Salesforce. There is no new permission model to learn. Why that last sentence matters so much Because AIforce reuses your permission model, it also reuses every shortcut hiding inside it. For years complexity worked as an accidental security layer. A rep who technically had access to a sensitive object rarely stumbled onto it, because finding it required the right report, the right list view and a bit of luck. Plain language removes that friction. One question in Slack and the data simply shows up. Picture a rep asking for every renewal above 50K closing this quarter that also has open support cases. If a permission set from a 2019 pilot still grants View All on Cases, the answer will include records that rep was never supposed to see. Nobody broke in. Your org did exactly what it was told. Before AIforce With AIforce Overexposed data was hard to find Overexposed data is one question away Admins built every view Users compose their own views Mistakes surfaced during audits Mistakes surface during conversations Cleanup could wait until next year Cleanup becomes urgent Five things to check before AIforce reaches your team 🔑Profiles and permission sets with View All or Modify All that nobody can justify today. 📋Sharing rules created for a single project years ago and never removed. 👥Public groups and role hierarchies that grew one exception at a time. 🔌Integration users with broad access and no clear owner. 🏦Field level security on truly sensitive fields like margin, compensation or personal data. Each of these takes an afternoon to review and a lot longer to explain after the fact. The good news is timing Salesforce is still finalizing AIforce pricing and packaging, which gives most orgs a comfortable window to get their house in order. Teams that use this window will enjoy the new interface from day one, while everyone else will be tempted to pause the rollout at the worst possible moment. Salesforce just gave your data a bigger voice, so make sure it only says what it should. Continue the series with meet the seven new Agentforce job ready agents, or see Salesforce Koa and the new multi model AI lineup. Dreamforce 2026AIforceSalesforce SecuritySalesforce AdminTrueSolv Share: LinkedIn Twitter / X Copy link In this article 01What AIforce actually does 02Why that matters so much 035 things to check 04The good news is timing Dreamforce 2026 coverage ← Full recap hub → You are here: AIforce & permissions Seven job ready agents Koa & multi-model AI Not sure what AIforce would expose? Book a Health Check focused on security and permissions before rollout. Book a Health Check → About the Author AR Anastasia RashkinaSalesforce Developer at TrueSolv
Dreamforce 2026 Announcements, Full Recap
More than 50,000 people came to Moscone Center, and over 122,000 more watched online. 🎤 Now the same question lands on every leadership team: what from all of that actually changes our Salesforce this year? We sorted the biggest Dreamforce 2026 announcements by the one thing that matters for planning — when they reach your org. The big picture in one paragraph Salesforce built the whole event around becoming an Agentic Enterprise and drew a clear four-layer stack. Data 360 holds data, metadata and memory. Customer 360 carries application logic. Agentforce runs the agents. On top sits the brand new AIforce, an interface layer that brings Salesforce data and actions into the tools people already use, starting with Slack and Claude, while keeping every existing permission and business rule in place. DREAMFORCE 2026 / THE STACK Slack Claude AIforce Interface layer, reaches Slack and Claude Agentforce, runs the agents Customer 360, application logic Data 360, data, metadata, memory Available now Beta or pilot Coming this fall Same permissions and business rules, all the way up the stack. Four layers, one architecture, reaching into the tools you already use. Available right now ✅ 🔀Multi Agent Orchestration is generally available, so several agents can pass work to each other instead of acting alone. 🤖Most of the new job ready agents are generally available, including Piper for inbound leads, Casey and Fin for service and customer experience, Carter for commerce, Marshall for back office and supply chain, and Paige for employee HR and IT requests. 🧠More model choice in Agentforce arrived with Amazon Bedrock models, plus Anthropic and NVIDIA models, available to Agentforce customers. 🗄Data 360 zero copy now reaches more AWS sources, including Apache Iceberg tables, Amazon Aurora, Amazon RDS and SageMaker Lakehouse. 📊Salesforce and Tableau inside Gemini Enterprise are live for Google Cloud customers. 📖The Well Architected Framework now has five pillars with an agentic lens, and it is probably the most practical free read of the week for architects. In beta or pilot 🧪 💬Salesforce in Claude is in beta on all paid Claude plans. 🧬Koa, the first Salesforce CRM reasoning model built together with NVIDIA, is piloting with select customers. General availability is expected in winter 2026 for US regions. 🔌Headless 360 MCP Server is in open beta, while the Data 360 MCP Server is already generally available. 🆕AIforce is officially announced, and Salesforce is still finalizing pricing and packaging. Coming this fall 📅 ⚙️Agent Optimizer is planned for October. 📣Campaign Agent is expected in Marketing Cloud Next Advanced by October 2026. 🎯Hunter, the outbound pipeline agent, is planned for general availability in November 2026. ☁️Hyperforce on Google Cloud is planned for general availability in North America in November 2026. 📞Agentforce Voice with Amazon Connect is due later this fall, and OpenAI models through Bedrock are on the way as well. Also worth knowing Salesforce kept growing its platform through acquisitions this year, with Contentful joining on September 1 and Fin, formerly known as Intercom, joining on September 10. That is also why one of the new customer agents carries the Fin name. What actually matters for a mid-sized org Big keynotes are built for every audience at once. A company with 50 to 500 Salesforce users usually needs only a slice of it, and this table shows where to look first. If your company is Focus on first Sales led with strong inbound demand Piper and a clean lead routing process Service heavy with a busy support queue Casey or Fin together with Multi Agent Orchestration Running on AWS or Google Cloud Zero copy data access and wider model choice Planning 2027 budgets right now AIforce readiness and a written AI model policy Three moves for this quarter 🔍Audit permissions and sharing. AIforce and every new agent run on the access you already have, so old shortcuts become visible much faster. 🎯Pick one workflow for one agent. Choose a process with a clear owner and a measurable outcome before anyone proposes a whole portfolio. 🧠Decide who chooses the model. With Koa, Claude, Gemini, OpenAI and Bedrock all on the table, write down which model runs which workload and where your data is allowed to go. This week we are breaking the biggest topics down in separate articles, starting with AIforce and permissions, then the seven new agents, then Koa and model choice. Start with AIforce and the permission cleanup it just made urgent, then see who’s on the roster in meet the seven new Agentforce job ready agents, and close it out with Salesforce Koa and the new multi model AI lineup. Dreamforce 2026 handed every Salesforce customer a bigger toolbox, and the teams that plan the first steps now will be the ones using it by spring. Dreamforce 2026SalesforceAgentforceSalesforce NewsTrueSolv Share: LinkedIn Twitter / X Copy link In this article —The big picture ✅Available right now 🧪In beta or pilot 📅Coming this fall —What matters for mid-sized orgs —Three moves this quarter Dreamforce 2026 coverage → You are here: Full recap hub AIforce & permission cleanup Seven job ready agents Koa & multi-model AI Timeline legend Available right now Beta or pilot Coming this fall About the Author ST Sergey TrusovCEO & Salesforce Architect at TrueSolv
Salesforce Integration Services, What the Work Involves
Sales lives in Salesforce, billing lives somewhere else, and someone spends every Friday afternoon reconciling the two by hand. That Friday afternoon reconciliation is the tell. Salesforce integration services connect the systems a team already relies on, billing, support, marketing, product data, so information moves automatically instead of getting copied by hand, and the person doing that copying gets their Friday back. SALESFORCE INTEGRATION / PROJECT STAGES Billing system 1 Data mapping 2 Sync architecture 3 Error handling 4 Sandbox testing 5 Monitoring Salesforce Real example, from our case studies Salesforce + Stripe, 6 weeks, renewals +28% Five stages between two disconnected systems and one live sync — mapping and architecture decided before anything is built. What disconnected systems actually cost The cost is not just the hour someone loses matching two spreadsheets. It’s the renewal risk that sits in a billing system for three days before sales ever sees it, or the field that gets mistyped during manual reconciliation and quietly feeds every report built on top of it afterward. A number that’s wrong on a Friday is wrong in every report pulled the following Monday, and by then nobody’s checking the original source anymore, they’re checking Salesforce. What a proper integration project actually involves 1Data mapping firstDeciding which system owns which field, and what happens when the two disagree, before a single line of integration code gets written 2Sync architecture chosen on purposeReal time API sync for anything time sensitive, a payment failure, a churn signal, and scheduled batch sync for anything that can wait a few hours, decided deliberately rather than defaulted to whichever is easier to build 3Error handling built in from the startThe other system will go down eventually, or send back something malformed, and a silent failure that nobody notices for a week is worse than a loud one that pages someone immediately 4Sandbox testing with data shaped like the real thingChecking both directions of the sync, not just the direction that was top of mind when the project got scoped 5Monitoring that continues after launchA sync that worked on day one and quietly stopped on day forty is the failure mode that costs the most trust, so something has to keep watching it What this looks like in practice TrueSolv connected Salesforce and Stripe for a UK fintech SaaS company in six weeks, syncing subscription and payment data directly onto Account records instead of leaving billing and sales to reconcile manually. Renewal rates rose 28 percent, and reconciliation time dropped by roughly three quarters. See the full Salesforce Stripe integration case study for the breakdown, from the discovery call to the churn alerts firing in production. A number that’s wrong on a Friday is wrong in every report pulled the following Monday. The fix isn’t a faster reconciliation process. It’s not needing one. Book an integration consultation through our contact form, and follow TrueSolv on LinkedIn for more Salesforce integration notes. Salesforce IntegrationSalesforce ConsultingCRM AutomationData SyncTrueSolv Share: LinkedIn Twitter / X Copy link In this article 01What disconnected systems cost 02What the work involves 03What this looks like in practice 5 project stages 1Data mapping 2Sync architecture 3Error handling 4Sandbox testing 5Monitoring Reconciling two systems by hand? Book a consultation to scope what connecting them would look like. Book a consultation → About the Author AS Anastasia RashkinaSalesforce Developer at TrueSolv
Dreamforce 2026, What to Expect September 15 to 17
Dreamforce returns to Moscone Center September 15 through 17, and this year the whole event is built around one idea, the agentic enterprise. Dreamforce 2026 runs September 15 through 17 at Moscone Center in San Francisco, with the full program also streaming free on Salesforce+ from September 15 through 18. The theme this year, Becoming an Agentic Enterprise, isn’t just a keynote tagline. It’s the lens the whole schedule of more than 1,600 sessions gets built around. DREAMFORCE 2026 / EVENT PREVIEW Becoming an Agentic Enterprise Moscone Center, SF Free on Salesforce+ 1,600+ sessions SEPTEMBER 2026 12-14 Bootcamp SEP 15 – 17 Dreamforce, on site SEP 18 Virtual extends Salesforce+ streams free, Sept 15 to 18 Opening keynote Tuesday Sept 15. TrueSolv covers the announcements the week after. One week, three days on site, one extra day to stream it free on Salesforce+. Quick facts In person, September 15 to 17 at Moscone Center, San Francisco, with a Trailblazer Bootcamp running September 12 to 14 beforehand. Free virtual access on Salesforce+, September 15 to 18, one day longer than the in-person event, with 400-plus sessions available live and on demand. Opening keynote Tuesday, September 15, historically where the year’s biggest product announcements land. What the theme means in practice Expect sessions organized around Agentforce 360, Salesforce’s unified platform bundling the Agentforce builder, Data 360, Customer 360 apps, and Slack into one connected stack. Less of the conference is going to be a single flashy agent demo this year, and more of it is going to be agents doing real multi-step work across sales, service, and operations at enterprise scale. Governance, observability, and adoption are set to get as much airtime as new features. What to actually watch if you’re not flying to San Francisco The opening keynote livestream on Tuesday is the highest value hour for anyone watching remotely. After that, the product-specific breakout recaps that surface over the following day or two tend to carry the detail the keynote skips, and the customer story sessions are where the actual deployment specifics, the parts that don’t make a highlight reel, tend to show up. Less of a single flashy agent demo this year, more agents doing real multi-step work across sales, service, and operations at enterprise scale. Governance and adoption get as much airtime as new features. TrueSolv will cover the biggest announcements the following week, so nobody has to sit through 1,600 sessions to find out what actually changed. Follow TrueSolv on LinkedIn and Instagram for Dreamforce coverage, and book a post-Dreamforce strategy call through our contact form once the announcements land. Dreamforce 2026SalesforceAgentforce AISalesforce CommunityTrueSolv Share: LinkedIn Twitter / X Copy link In this article 01Quick facts 02What the theme means 03What to watch remotely Dreamforce 2026 Sep 15–17 Moscone Center, San FranciscoBootcamp: Sep 12–14Free on Salesforce+: Sep 15–18 Want the announcements decoded? Book a post-Dreamforce strategy call once the news lands. Book a strategy call → About the Author AS Anastasia SokolovaSalesforce Developer at TrueSolv
HubSpot to Salesforce Migration, What to Prepare First
Most rocky HubSpot to Salesforce migrations fail on the field mapping nobody planned for, not on the data transfer itself. A HubSpot to Salesforce migration typically takes four to eight weeks for a straightforward setup, longer if the org carries years of custom properties and workflow automation. TrueSolv’s own migrations tend to land near that low end. A Series A SaaS company with 25 users moved over in four weeks with zero data loss and pipeline visibility up 40 percent afterward. What decides which end of that range a project lands on is preparation, not the transfer itself. HUBSPOT TO SALESFORCE / MIGRATION PATH HubSpot 1 Audit 2 Map fields 3 Dedupe 4 Sandbox test 5 Phased go live Salesforce 4 TO 8 WEEKS TYPICAL A 25-user Series A org moved in 4 weeks, zero data loss, pipeline visibility up 40%. Five checkpoints between HubSpot and a Salesforce org that’s actually ready — audit, map, dedupe, test, then go live. Audit the HubSpot data before anything moves Pull a full inventory of every custom property, workflow, and integration currently live in HubSpot. Flag which properties are actually in use versus abandoned years ago and never cleaned up. Check for duplicate contacts and companies that have built up over time. Note every HubSpot workflow that touches an external system, like billing or marketing automation, since each one needs a Salesforce equivalent before cutover. Map fields and objects on purpose, not by matching names HubSpot’s Contacts, Companies, and Deals don’t sit one to one on Salesforce’s Leads, Contacts, Accounts, and Opportunities, and deal stages rarely line up cleanly between the two platforms. A field like Lifecycle Stage in HubSpot might need to split across two or three Salesforce fields depending on how sales actually uses it day to day. This is the step most rushed migrations skip, and it’s where the rocky ones go wrong. Not in the data transfer itself, in the decisions about where each piece of data is supposed to live once it arrives. Deduplicate and clean up before the move, not after Migrating duplicates into Salesforce just starts the new CRM with the same mess under a new name. Run matching rules on the HubSpot export before load, email domain plus company name catches most of it, with phone number normalization for the rest. Decide on one source of truth for any field where HubSpot and another connected system disagree, and archive records that haven’t been touched in years instead of migrating everything on principle. Test the whole thing in a sandbox before it’s real Load a representative sample, or the full dataset, into a Salesforce sandbox first. Have the sales team run their actual daily workflow there, creating a deal, logging a call, pulling a report, before anyone touches production. Confirm that automation like assignment rules and email alerts fires correctly on migrated records. Mapping errors caught here cost nothing. The same errors found in production cost trust, and sometimes a deal. A phased go-live that doesn’t stop a deal mid-conversation 📦Move closed and historical data first, since nobody is actively working it ⏱Run HubSpot and Salesforce in parallel for open deals during a short transition window 🗓Cut active pipeline over in one scheduled move, often a weekend, so no rep loses a deal mid-conversation 🔒Keep HubSpot in read-only access for a defined period after cutover, in case something was missed 📢Tell the sales team the exact cutover time, so nobody logs a deal into the old system out of habit Four weeks is realistic. Eight is normal. Both numbers depend almost entirely on how much of this happens before the first record actually moves, not on how fast the transfer itself can run. Book a free migration consultation through our contact form, and follow TrueSolv on LinkedIn for more Salesforce admin and developer notes. Salesforce MigrationHubSpotCRM MigrationSalesforce ConsultingTrueSolv Share: LinkedIn Twitter / X Copy link In this article 01Audit the HubSpot data 02Map fields on purpose 03Deduplicate before the move 04Test in a sandbox 05A phased go-live 5 checkpoints 1Audit 2Map fields 3Dedupe 4Sandbox test 5Phased go live Planning a HubSpot → Salesforce move? Book a free consultation to scope the timeline before you commit to one. Book a consultation → About the Author AS Anastasia SokolovaSalesforce Developer at TrueSolv
Agentforce Implementation, Where to Actually Start
Everyone is talking about autonomous agents in Salesforce, but few teams can name one concrete first step. The honest answer to where to start with Agentforce implementation is with one workflow, not a strategy. Pick a single repetitive task your team can already describe clearly, ground the agent in Salesforce data and content you already trust, and get that one agent live before touching a second use case. AGENTFORCE IMPLEMENTATION / FIRST STEP TODAY Manual workflow Readiness assessment Blueprint & grounding First live agent WHERE TEAMS ACTUALLY START Case deflection Email drafting Agent-assisted replies Start narrow. One workflow, one agent, a human still in the loop. From today’s manual step to a first live agent — readiness assessment, blueprint, then go live. What Agentforce can actually do right now Agentforce uses the automations and integrations already in your Salesforce org as callable actions, then pairs those actions with answers pulled from your CRM data and approved content. It works inside topics and routing you define, not as an open-ended assistant that figures out your business on its own. That’s not a limitation to apologize for. It’s what makes an agent’s answers traceable back to data your business actually owns, instead of a plausible-sounding guess. Where teams actually start 💬Case deflectionThe agent answers common support questions from your knowledge base before a ticket ever reaches a human queue. ✉️Email draftingThe agent prepares a first-pass reply grounded in the case history, and a rep reviews it before anything goes out. 🤝Agent-assisted repliesInside Slack or the service console, the agent surfaces a likely answer with its source, and a person still makes the call. Every one of these keeps a human in the loop on the first pass. That’s by design. The point of a first use case is proving the agent’s answers hold up against real questions, not handing it the keys on day one. What an Agentforce implementation with TrueSolv involves It starts with a readiness assessment, a review of your org, data sources, and target workflows to confirm what Agentforce can support now and what needs prep first. From there, a use case workshop turns one workflow into a clear blueprint, with topics, allowed actions, handoff rules, and success metrics defined before any building starts. Data grounding comes next, configuring the agent to answer from your Salesforce data and approved sources, alongside a knowledge cleanup pass so it pulls one consistent answer instead of three conflicting versions. Agent Builder configuration sets up the topic structure, routing, and guardrails, and a Flow and Apex action library lets the agent actually complete tasks inside Salesforce, not just talk about them. Structured testing on topic and action selection runs before rollout, and monitoring stays on after go-live so the agent keeps improving on real usage instead of staying frozen at launch. The point of a first use case is proving the agent’s answers hold up against real questions, not handing it the keys on day one. Book an Agentforce readiness call through our contact form, and follow TrueSolv on LinkedIn for more on where this technology is actually ready today. AgentforceSalesforce AIAI AgentsSalesforce ConsultingTrueSolv Share: LinkedIn Twitter / X Copy link In this article 01What Agentforce can do now 02Where teams actually start 03What implementation involves Implementation steps 1Readiness assessment 2Use case workshop & blueprint 3Data grounding & KB cleanup 4Agent Builder configuration 5Testing & rollout 6Monitoring after go-live Ready for a first agent? Book a readiness call to scope one workflow and get a real blueprint. Book a readiness call → About the Author AS Anastasia SokolovaSalesforce Developer at TrueSolv
Task Tracker Salesforce App That Keeps Deadlines Visible
Tasks live in Trello or Asana, deals live in Salesforce, and the manager finds out about a missed deadline last. A task tracker Salesforce app fixes that by keeping tasks, due dates, and priorities on the same record as the deal or case they belong to, so a missed deadline shows up on the account itself instead of surfacing three tools away, days after it mattered. OUTSIDE SALESFORCE Trello / Asana board Email thread ! Manager finds out last True Task Tracker SALESFORCE Task & due date Priority tag Comments & files One task list, tied to the deal it belongs to. Trello board, email thread, and a manager finding out last — all replaced by one task list on the Salesforce record. Why splitting tasks and CRM data costs more than convenience A rep works from a board in one tab while the deal record sits open in another, and the two never fully sync. A task gets marked done in Trello and the opportunity record never reflects it. A follow-up call slips because the person who owns the deal isn’t the person watching the board, and the two tools were never going to tell each other. That’s not a discipline problem. It’s a system problem. Two tools with two sources of truth will always drift, and the gap between them always costs someone — a rep who missed a follow-up, a manager scanning a pipeline that doesn’t show the half-overdue task still sitting in Asana. What comes with it True Task Tracker — what’s included 📋Tasks created, assigned, and managed with due dates — right on the record they belong to, no separate login 🏷Flexible tags to prioritize and categorize, plus custom columns for how your team actually works 🔔Instant notifications when a task changes, so a status update doesn’t wait to be noticed hours later in a different tool 📎Files and comments attached directly to the task, instead of scattered across email threads and Slack conversations ↕️Drag-and-drop task movement for updating status without a form to fill out — the way boards work, inside Salesforce Who gets the clearest win A sales team gets the clearest result first. Follow-up tasks sit directly on the opportunity, so a manager scanning the pipeline sees exactly which deals have an overdue task without opening a separate board to check. A support team benefits just as much. Escalation tasks get assigned with a due date and a priority tag right on the case, and the comments and attachments that explain the escalation stay with it instead of living in three different Slack threads. The support lead sees what’s overdue, who owns it, and why it was flagged — all from the same record view they’re already in. The deadline was always real. Now it lives where the deal does. Request a True Task Tracker demo through our contact form, and follow TrueSolv on LinkedIn and Instagram for more tools built to keep work inside Salesforce. True Task TrackerSalesforce ProductivitySales OpsCRM ToolsTrueSolv Share: LinkedIn Twitter / X Copy link In this article 01Why splitting tools costs more 02What’s included 03Who gets the clearest win Deadlines still living in a separate board? True Task Tracker puts tasks, due dates, and priorities directly on the Salesforce record. Request a demo → 5 things included 📋Tasks + due dates on the record 🏷Flexible tags + custom columns 🔔Instant notifications on change 📎Files + comments on the task ↕️Drag-and-drop status update About the Author DS Daria SavelievaSalesforce Consultant & Content Lead at TrueSolv
Apex Unit Test Best Practices Beyond the Coverage Number
Plenty of orgs hit the 75 percent coverage requirement with tests that check nothing real at all. Coverage counts which lines of code ran during a test, not whether the test verified anything meaningful. A test that inserts a record, calls a method, and confirms only that no exception was thrown will happily push coverage past 75 percent while catching zero actual regressions. Real Apex unit test best practices start from a different question: whether the test would fail the moment the underlying logic breaks, not whether it satisfies a percentage. APEX TESTING / CI PIPELINE 75% Coverage number alone Real assertions Bulk data, 200+ Mocked callouts CI gate Deploy What actually gates the merge Assertions tied to business outcome, not just the absence of an error 200+ record bulk test on every method that touches DML or SOQL External callouts mocked, never live inside a test context From a 75% coverage number to a CI gate that actually stops a broken assumption from shipping. The gap between passing and protecting A weak test looks productive. It compiles, it runs, it shows green in the deployment log, and the coverage number goes up. What it usually skips is any assertion tied to business outcome. It checks that a record exists, not that a field landed on the value the logic was supposed to produce. Six months later, someone changes a trigger, every existing test still passes, and the bug ships anyway — because nothing in the suite was actually watching for it. Assert patterns that actually catch something A test worth keeping asserts on the specific outcome the code is supposed to produce, not just on the absence of an error. That means asserting the field value that should have changed, the record count that should have resulted, or the exception that should have been thrown on a bad input. Here is a pair of tests for a trigger that updates a custom forecast category once an opportunity crosses an amount threshold. @isTest private class OpportunityRoundingTest { @isTest static void updatesForecastWhenAmountChanges() { Account acc = new Account(Name = ‘Test Account’); insert acc; Opportunity opp = new Opportunity( Name = ‘Renewal Deal’, AccountId = acc.Id, StageName = ‘Prospecting’, CloseDate = Date.today().addDays(30), Amount = 10000 ); insert opp; Test.startTest(); opp.Amount = 25000; update opp; Test.stopTest(); Opportunity updated = [ SELECT Forecast_Category_Custom__c, Amount FROM Opportunity WHERE Id = :opp.Id ]; Assert.areEqual(25000, updated.Amount, ‘Amount should reflect the update’); Assert.areEqual(‘Best Case’, updated.Forecast_Category_Custom__c, ‘Forecast category should move once the deal crosses the threshold’); } @isTest static void doesNotDefaultAmountWhenLeftBlank() { Account acc = new Account(Name = ‘Test Account 2’); insert acc; Opportunity opp = new Opportunity( Name = ‘Early Deal’, AccountId = acc.Id, StageName = ‘Prospecting’, CloseDate = Date.today().addDays(60) ); Test.startTest(); insert opp; Test.stopTest(); Opportunity result = [SELECT Amount FROM Opportunity WHERE Id = :opp.Id]; Assert.isNull(result.Amount, ‘A deal with no amount should stay null, not default to zero’); } } Both tests assert on the actual business rule — the forecast threshold and the null default — not just on the record existing. Bulk data catches what a single record never will A test that inserts one record will pass even when the underlying code runs a query or a DML statement inside a loop, because one iteration never comes close to a governor limit. Two hundred records will. Building bulk data into a test is the difference between finding that bug in a sandbox and finding it in production during a mass import. @isTest static void handlesBulkInsertWithoutHittingLimits() { List<Account> accounts = new List<Account>(); for (Integer i = 0; i < 200; i++) { accounts.add(new Account(Name = ‘Bulk Account ‘ + i)); } Test.startTest(); insert accounts; Test.stopTest(); List<Account> inserted = [ SELECT Id FROM Account WHERE Name LIKE ‘Bulk Account%’ ]; Assert.areEqual(200, inserted.size(), ‘All 200 accounts should insert without hitting a governor limit’); } Mocking callouts without touching a real endpoint Any test that reaches out to a real external system is slow, flaky, and eventually blocked by Salesforce itself, since live callouts aren’t allowed inside a test context. The fix is the HttpCalloutMock interface, which lets a test hand back a fake response and check that the code parses and handles it correctly — success and failure alike. @isTest private class ShippingRateMockTest { private class SuccessMock implements HttpCalloutMock { public HttpResponse respond(HttpRequest req) { HttpResponse res = new HttpResponse(); res.setStatusCode(200); res.setBody(‘{“rate”: 14.50, “carrier”: “Standard”}’); return res; } } @isTest static void parsesRateFromSuccessfulCallout() { Test.setMock(HttpCalloutMock.class, new SuccessMock()); Test.startTest(); ShippingRate rate = ShippingService.getRate(‘90210’); Test.stopTest(); Assert.areEqual(14.50, rate.amount, ‘Rate should match the mocked response body’); Assert.areEqual(‘Standard’, rate.carrier, ‘Carrier should be parsed from the JSON response’); } } A second mock returning a 500 status covers the failure path that actually breaks integrations in production. Wiring tests into CI before anything merges None of this holds up if tests only run when someone remembers to run them by hand. Wiring Apex tests into a CI pipeline means every pull request triggers a deploy to a scratch org or sandbox followed by a full test run, and a merge simply can’t happen if a test fails or coverage drops below the threshold. name: apex-tests on: [pull_request] jobs: test: runs-on: ubuntu-latest steps: – uses: actions/checkout@v4 – run: sf org login sfdx-url –sfdx-url-file authFile.txt –alias ci-org – run: sf project deploy start –target-org ci-org – run: sf apex run test –target-org ci-org –code-coverage –result-format human –wait 20 A coverage number without CI is a report nobody reads until deploy day. A coverage number wired into every pull request is a gate that actually stops a broken assumption from shipping. Send your test suite our way through the contact form for a custom development and code review pass, and follow TrueSolv on LinkedIn for more Apex notes. Apex CodeSalesforce DevCRM DevelopmentSalesforce TestingTrueSolv Share: LinkedIn Twitter / X Copy link In this article 01Passing vs protecting 02Assert patterns that work 03Bulk data (200+ records) 04Mocking callouts 05Wiring into CI What actually gates the merge Assertions on business outcomes — not just “no exception” Bulk data
TrueSolv 7th Anniversary. Here Is What We Are Doing With Them.
Seven years ago TrueSolv started with a laptop, a Salesforce login, and considerably more confidence than clients. The anniversary was Sunday. This post is the Monday version. We are marking it the way that actually matters to you — not with a party you cannot attend, but with free hours on your Salesforce org. No strings, no upsell script, just work that needs doing. 7 Seven Years in the Making Founded in Tbilisi, Georgia · Also operating from Dubai, UAE 7years of Salesforce implementation, development, and consulting 2countries · 1 distributed team · 1 timezone gap that somehow works 7industries served across the client portfolio Industries: NonprofitFintechHealthcareSaaSRoboticsLegalReal estate What seven years of Salesforce consulting actually looks like TrueSolv was founded in Tbilisi, Georgia, and now operates across Tbilisi and Dubai. Seven years in a single industry gives you a particular kind of longitudinal view: you see the same problems appear in different clients, at different stages, in different industries, in the same repeating patterns. You also see how the platform changes underneath the work. When we started, the conversation was Classic versus Lightning and whether Lightning was actually ready. Now the conversation is how Agentforce agents should be scoped and what the data quality requirements are for a reliable AI deployment. The specific questions change; the underlying work — understanding what a business needs from Salesforce and building it correctly — stays constant. We have worked across nonprofits, fintech companies, healthcare teams, SaaS businesses, robotics companies, legal firms, and real estate operations. The industries are different. The version of “we built something that worked and then something changed and now it does not quite work anymore” is surprisingly consistent across all of them. To every client who brought us that problem over the past seven years: thank you. The challenging ones especially. You are the reason we got better at this. The campaign: free Salesforce work through August 10 From July 27 through August 10, TrueSolv is offering free Salesforce work under four hours. No minimum commitment, no catch. If the job takes longer than four hours, the first four hours are still free — you only pay for anything beyond that, and we will tell you before we go further. What four hours actually covers What four free hours can actually coverNo projects, no retainers — just work that needs doing, this week, for free ⚙️A stuck automationA Flow that fires at the wrong time, a process that was working six months ago and stopped, an integration that produces errors nobody has tracked down. 🔐A permission issueA user who should see something and cannot. A user who can see something they should not. A profile configuration question that has been bouncing between your team and Salesforce support. 📊A report that never works rightThe numbers do not match what your team expects, the filters are not doing what they look like they should be doing, a dashboard that someone decided to trust and probably should not. ✅A configuration change on the backlogSomething small that would make the CRM noticeably better for the people using it every day, but has been sitting on a list because nobody has gotten to it. These are not the kinds of problems that require a multi-week project. They require someone who knows Salesforce to look at them without billing pressure. That is what the free hours are for. 🎂 7th Anniversary Free Hours CampaignEnds Aug 10 4Free hours on your Salesforce org — no minimum commitment, no catch Aug 10Campaign closes — this week only If the job takes longer than 4 hours, the first 4 are still free. You only pay for anything beyond — and we tell you before we go further. Seven years is a good time to do something useful. Book your free hours at truesolv.com before August 10 — no strings, no catch. Follow us on LinkedIn and Instagram — we will be sharing more from the last seven years all month. TrueSolvSalesforce Consulting7 Year AnniversaryFree Consultation Share: LinkedIn Twitter / X Copy link In this article 01Seven years of consulting 02The free-hours campaign 03What 4 hours covers 🎂 Anniversary Offer 4 free hours on your Salesforce org No strings. No catch. Through August 10 only. Claim your free hours → About the Author AR Anastasia RashkunaMarketing Specialist & Author at TrueSolv
Salesforce Field History AI Readiness
An Agentforce agent grounded in your Salesforce data will give answers based on whatever your records contain. If a field was overwritten six weeks ago by a bad import, the agent does not know that. If a contact’s status was manually edited three times without a logged reason, the agent treats the current value as correct. Your AI is only as trustworthy as your data history. True Field History is how you know what your data actually is. Opportunity Field History — What the Agent Sees vs. What Actually Happened What the Agentforce agent sees CurrentOpportunity StageProposal SentLast changed: 18 days ago CurrentAmount$45,000No recent changes noted CurrentClose DateAug 31, 2026Set at opportunity creation Agent readAgent assessmentDeal progressing — moderate paceNo risk flags surfaced What the field history actually shows 8 days agoStage was moved backVerbal Commit → Proposal SentNo reason logged. Changed by rep. 12 days agoAmount was reduced$78,000 → $45,000No reason logged. Changed by rep. 15 days agoLast activity loggedEmail sent — no responseNo follow-up logged since RealityActual risk profileStage regression + amount cut + 15 days darkSignificant risk. Agent had no visibility into this. The agent saw three fields and assessed normal deal progression with no risk flags. The field history shows a stage regression, a significant amount reduction, and 15 days of no contact — all without logged reasons. The AI data trust problem most deployments skip When organisations deploy Agentforce, the configuration conversation focuses on agent topics, knowledge base grounding, escalation logic, and Trust Layer guardrails. These are the right things to configure. What most organisations underestimate is the quality and reliability of the data the agent is reasoning from. An Agentforce agent does not evaluate data quality. It does not flag uncertainty about data recency. It does not know that the contract end date on an account was changed two months ago from a correct value to an incorrect one during a data cleanup task that went wrong. It presents what it finds and reasons from it as if it is accurate. This is not an agent problem. It is a data problem that the agent makes visible in a new way: not as a messy CRM that someone will clean up eventually, but as an AI system that answers incorrectly right now. Three scenarios where field history and Agentforce intersect 💚Customer Health ScoringAgent reasons from activity fields Specific vulnerabilityLast Contacted fields edited by reps to satisfy KPIs or look better in pipeline reviews. Agent reads the edited date, computes recency, produces a health score built on fabricated history.→ Field history reveals: accounts where Last Contacted was manually edited without a corresponding logged activity. 📋Contract Renewal AgentAgent triggers from contract dates Specific vulnerabilityInformal renegotiations that change terms verbally but never update the contract end date in Salesforce. Agent fires renewal outreach at the original date for a contract already renegotiated.→ Field history reveals: contract end dates not updated despite account activity suggesting renegotiation. 📊Pipeline & Deal RiskAgent reasons from stage and amount Specific vulnerabilityStage regressions and Amount reductions with no logged reason. Agent sees current stage and amount, assesses normal progression, misses the risk pattern entirely visible only in the change log.→ Field history reveals: stage regressions, amount cuts preceding a stage change, patterns inconsistent with deal movement. Scenario 1: Customer health scoring agents A customer health scoring agent ingests activity data — last contacted date, meeting count, support ticket volume, product usage signals — and produces a health score or churn risk flag that surfaces in account management workflows. The specific vulnerability is in manually managed fields: Last Contacted date fields that can be edited by reps. True Field History exposes this pattern before the agent is grounded in it. Scenario 2: Contract renewal agents A renewal agent monitors contract end dates and triggers outreach at defined thresholds before expiration. The common failure mode is informal renegotiations where the AE updates pricing in a side document, verbally confirms new terms, but never updates the contract end date in Salesforce. The renewal agent fires at the original date, triggering outreach for a contract that was already renegotiated. A renewal audit using field history takes 20 minutes and catches this problem before the agent encounters it. Scenario 3: Pipeline and deal risk agents An agent surfacing deal risk and stage progression analysis needs Opportunity Stage and Amount fields to reflect current deal reality. These are two of the most commonly manipulated fields in Salesforce. An agent reviewing an Opportunity that shows Stage: Proposal Sent, Amount: $45,000, Last Stage Change: 3 weeks ago will flag that deal as progressing normally. If the actual history shows the Stage was at Verbal Commit 10 days ago before being moved back without a logged reason, the risk profile is completely different — and the agent has no way to know. The broader argument for a pre-AI field history audit The three scenarios above share a structural pattern: a field value that looks correct in the current record is unreliable because of how it arrived at the current value — overwritten, manually edited without reason, or changed in a way that is inconsistent with the surrounding activity log. None of these problems are visible by looking at the current record. All of them are visible in the field change history. A pre-AI deployment field history audit identifies which fields the agent will reason from, which of those fields have unreliable change histories, and what data quality remediation is needed before the agent is grounded in those fields. For a focused Agentforce deployment — an agent reasoning from a defined set of Account and Opportunity fields — the relevant field history can be reviewed and flagged in days. Pre-AI Deployment Field History AuditRun this before grounding any Agentforce agent in Salesforce data Map what the agent will reason from List the specific fields the agent will access for each topicEvery field in the agent’s grounding scope is a data quality risk. Make the list explicit before the audit — not all