Field Notes

Build logs, not thought leadership.

Field Notes is the Nocona Consulting build log — what is actually being built, written down as it happens, with the metadata, the diagrams, and the decisions that did not survive first contact.

  • Action overrides
  • Address
  • Anonymous Apex
  • Apex
  • Apex testing
  • Asset
  • AssetWarranty
  • AssociatedLocation
  • Aura
  • Before-save flow
  • Billing
  • Content Security Policy
  • Custom Metadata Types
  • Data loading
  • Data model
  • Data quality
  • Deployment
  • Destructive changes
  • Duplicate rules
  • Dynamic Forms
  • Email Services
  • External Credentials
  • Field Service
  • Field-level security
  • Flow
  • Flow formulas
  • Flow versions
  • Forecasting
  • Global value sets
  • Greenfield
  • Households
  • Integration
  • Junction objects
  • Lead
  • Lead conversion
  • Lightning Web Components
  • Lightning record pages
  • Location
  • Lookup filters
  • Managed packages
  • Metadata
  • Metadata API
  • Multi-select picklists
  • Named Credentials
  • Object model
  • Open CTI
  • Opportunity
  • Order
  • Order Products
  • Page layouts
  • Permission sets
  • Person Accounts
  • Picklists
  • Platform Cache
  • Process
  • ProductConsumed
  • Queueable
  • Queueable Apex
  • Quick actions
  • Quote
  • Record types
  • Release management
  • Reporting
  • Revenue reporting
  • RingCentral
  • SFDX
  • SOSL
  • Sales processes
  • Schedulable
  • Scheduling
  • Screen Flow
  • Screen flows
  • Service Appointment
  • Setup
  • Source control
  • StandardValueSet
  • State and Country/Territory Picklists
  • Testing
  • Tooling API
  • Triggers
  • Warranty
  • Work Order
  • Work Type
  • WorkOrder
  • WorkOrderLineItem

Latest

Archive

Build log Doorvana

Hiding five fields on one record type took a whole Dynamic Forms conversion

Installers kept seeing repair-only fields on new-construction Opportunities. Rather than a second page layout and profile layout assignments, the Opportunity Lightning record page was converted from force:detailPanel to Dynamic Forms, with a component visibility rule on {!Record.RecordType.DeveloperName}. How the layout was turned into flexipage:fieldSection facets, why the Account card failed validation with "missing required property [updateQuickActionName]" and then "Could not find quick action [Account._LightningUpdateAccount]", the GlobalValueSet default that changed three objects at once, and why the page layout stops mattering afterwards.

  • Dynamic Forms
  • Lightning record pages
  • Record types
  • Page layouts
Build log Doorvana

The release couldn't ship because the phone sync was running

A full-release redeploy that had always been safe to repeat failed production validation with 18 errors before a single test ran: "This schedulable class has jobs pending or in progress". A scheduled RingCentral sync locked its own classes and everything around them, none of which had changed. Why Type.forName in the Schedulable did not help, the Deployment Settings bypass I chose not to use, shipping a smaller manifest with sf project deploy validate and quick deploy, the EmailServicesAddress that is not metadata, and the stop-deploy-reschedule routine for when the scheduled code itself changes.

  • Apex
  • Schedulable
  • Deployment
  • Release management
Build log Doorvana

The release passed every check. Every flow in it was switched off.

A sales release validated 29 of 29 tests and deployed Succeeded, and the first real lead converted wrong four different ways. All 13 flows had landed in production as Draft, because production deploys flows inactive unless "Deploy processes and flows as active" is on. Why the validation could not notice, how a FlowDefinition Tooling API query found it, the prod-safe smoke test that now fails when flows are not active, and the record type picklist default that was a separate bug hiding in the same symptoms.

  • Flow
  • Deployment
  • Apex testing
  • Lead conversion
Build log Doorvana

The recording was right there, and the player sat at 0:00

Streaming RingCentral call recordings into a Lightning Web Component without storing them in Salesforce. Why a data: URL player never loads (Content Security Policy media-src), why a 6 MB recording cannot pass through one Apex transaction, how HTTP Range requests and a Blob in the browser get around the heap limit, and why every chunk requesting its own access token would have hit a 429 within a minute.

  • Lightning Web Components
  • Content Security Policy
  • Apex
  • Platform Cache
Build log Doorvana

The office phone rang all day. None of it reached Salesforce.

The RingCentral managed package is an Open CTI softphone. It logs calls handled in a signed-in user's browser tab, not calls that ring desk phones. Why it never saw the office line, the CTI Adapter URL that showed "This content is blocked" in a sandbox, and the server-side sync that replaced it: JWT auth through an External Credential, twelve scheduled jobs, upsert on an external ID, SOSL IN PHONE FIELDS matching, and the deploy lock a running schedule puts on its own code (corrected: Type.forName did not lift it).

  • RingCentral
  • Open CTI
  • Named Credentials
  • Queueable Apex
Build log Doorvana

The form stopped asking. Every old version of it still did.

The client changed two intake decisions overnight: one Builder Homeowner lead source instead of two values, and no door counts on the Lead. Retiring a LeadSource value through a StandardValueSet deploy, the test that would have passed against a retired value, and the field delete that failed because flow versions that can never run again still held references to it.

  • Flow
  • Flow versions
  • Destructive changes
  • Lead
Build log Doorvana

You can't name a job after an address it hasn't been told yet

Converted Opportunities were supposed to read as the street and the line of business. Lead conversion creates the Opportunity before the property exists, so a before-save flow on create never sees it. How the naming moved to the update that follows, how repeat jobs keep their numbers through a rename, what standard conversion does to the Account billing address, the one-word picklist default that would have turned every builder's office into a job site, and why a name ending in a dash turned out to be the data, not the flow.

  • Lead conversion
  • Flow
  • Before-save flow
  • Opportunity
Build log Doorvana

The form showed Texas. The record had no state.

A screen flow swapped typed address fields for the Address component with Google address lookup. The suggestion filled Street, City, State and ZIP on screen, the deploy succeeded, every test passed, and the Lead saved with StateCode blank. What the lookup actually returns in province and country, how to map it to State and StateCode, and why an update needs the code alone.

  • Flow
  • Screen flows
  • Address
  • State and Country/Territory Picklists
Build log Doorvana

The form with no Next button

A screen flow that replaces the Lead New action had three screens with allowFinish set to false. The footer rendered, empty, and nobody could get past screen one. Why allowFinish governs the Next button too, the blank screen input that IsNull never matched, and the connector that looped back and erased everything the user had typed.

  • Flow
  • Screen flows
  • Lead
  • Aura
Build log Doorvana

Renaming the business before anyone depends on the old words

The client renamed his lines of business before anything had reached production. Which API names to change and which to only relabel, renaming an Opportunity record type through the Tooling API without changing its Id, the 11 fields a non-admin could not see, and two deploy failures on the way to a check-only validation against production.

  • Record types
  • Global value sets
  • Tooling API
  • Field-level security
Build log Doorvana

One Lead record type, and the values it never offered

Builder prospects and homeowner service requests share a single Lead record type, told apart by a Customer Type field. The decision is sound and it is not free: picklist values the field had and the record type never enabled, REQUIRED_FIELD_MISSING on a builder insert, a conversion flow about to turn a builder's office into a job site, and an Opportunity that lands on the wrong record type.

  • Record types
  • Picklists
  • Lead conversion
  • Flow
Build log Doorvana

The call was logged. The nurture tag silently never happened.

A subflow tags a builder for nurture when the call outcome is Existing Installer. The first formula would not deploy because it touched a multi-select picklist. The second deployed, ran without a fault, updated every other field in the same assignment, and wrote null. How it was found, why getVariableValue could not see it, and the nested IF that fixed it.

  • Flow
  • Flow formulas
  • Multi-select picklists
  • Lead
Build log Doorvana

The job was booked and the crew was never told

Closed Won produced an Order and an install Work Order, and the dispatch board stayed empty, because a Work Order is not a thing anyone can schedule. Creating the ServiceAppointment in Apex rather than switching on ShouldAutoCreateSvcAppt, and the silent SaveResult that cost an afternoon on the way.

  • Field Service
  • Service Appointment
  • Work Type
  • Apex
Architecture Doorvana

Two doors, one trip fee, and the fields that were on the wrong object

A warranty network's diagnosis checklist was planned as seven fields on WorkOrderLineItem. Two of them belong on the Work Order instead, because the trip fee is charged once per visit however many doors get diagnosed — and the question that settles it is cardinality, not the requirement document.

  • Field Service
  • WorkOrderLineItem
  • WorkOrder
  • Data model
Build log Doorvana

Winning the bid books the order and starts the install — exactly once

Closed Won on a construction bid has to produce a booked Order and an install job, and the install must never bill a second time when the crew finishes. Two independent automations cooperate through one standard field that neither of them owns: WorkOrderLineItem.OrderId.

  • Opportunity
  • Order
  • Quote
  • Field Service
Build log Doorvana

The job is not finished when the first visit is

A two-visit repair bills once, when the Work Order completes. A technician who taps Completed at the end of visit one invoices the diagnosis and nothing else, and the spring fitted on Thursday never reaches an invoice. The guard that stops it once the return visit is on the job, the status that had to exist before blocking anything was reasonable, and the case no guard of this kind can see.

  • Field Service
  • Apex
  • Work Order
  • Service Appointment
Build log Doorvana

One dropdown took one element. The one next to it took four.

Two dropdowns on the same screen flow, identical to the user. One is a record choice set. The other has to reach a Location through AssociatedLocation, which no record choice set can do — and the metadata element for the thing that can does not exist under the name you would guess.

  • Flow
  • Field Service
  • AssociatedLocation
  • Metadata API
Architecture Doorvana

The builder does not change when the house sells

Whether a garage door call is warranty or billable depends on who bought the door, not who owns the house. One extra lookup on Location is what makes that answerable — and one custom warranty date field that had to be deleted the next day.

  • Location
  • Asset
  • Warranty
  • AssetWarranty
Build log Doorvana

The note said Built. It had never been deployed.

Five deploy errors, one cause. A foundational custom field and its global value set were written, committed, and never deployed — and every later piece of work assumed they existed. A dry-run found in seconds what reading the source never could.

  • SFDX
  • Source control
  • Deployment
  • Global value sets
Build log Doorvana

I reported a duplicate-rule problem that did not exist

A test failed with DUPLICATES_DETECTED, so the rules were obviously set to block. They were not. Database.DMLOptions carries allowSave, but setOptions does not carry the duplicate-rule header — only the Database.insert overload does, and by default that overload does not throw when the save fails for some other reason.

  • Apex
  • Duplicate rules
  • Testing
  • Metadata API
Build log Doorvana

Two fields both called state, and only one of them will take TN

With State and Country/Territory Picklists on, Lead.State holds Tennessee and Lead.StateCode holds TN. A Flow copying the wrong one into a restricted picklist looked correct, deployed clean, and would have failed every enquiry with an address on it.

  • Flow
  • Picklists
  • Global value sets
  • Location
Build log Doorvana

The dropdown offered a value the save refused

A screen flow built its Request Type dropdown from a picklist choice set, which returns the whole value set. The record type on Lead allowed a narrower list. The form offered New Construction and the save rejected it — and one of three lines of business had no route into the org at all.

  • Flow
  • Record types
  • Picklists
  • Screen flows
Build log Doorvana

I reported four missing standard fields. All four exist.

No such column 'BillToContactId' on entity 'Order' is a sentence you believe. Under API 67.0 user mode it also fires for a field that exists and that your profile simply cannot see — and sf sobject describe hides both cases identically.

  • Apex
  • Field-level security
  • Tooling API
  • Order
Build log Doorvana

The parts filter that read correctly and would have billed nothing

A billing bridge filtered parts on IsConsumed = true, which reads like parts that were used. It means parts that came out of inventory. For a company with no warehouse it is false forever, and every spring would have fallen off every invoice without a single error.

  • Field Service
  • Apex
  • Billing
  • ProductConsumed
Build log Doorvana

Putting the org in git found a forecasting bug nobody had noticed

Three Opportunity stages carried forecastCategory=Closed, so open pipeline was sitting in the Closed bucket. Nobody spotted it in the UI. The metadata retrieve showed it in one line.

  • Forecasting
  • Source control
  • Opportunity
  • Sales processes
Architecture Doorvana

The multi-select picklist that could not survive its own success

A multi-select picklist caps at 150 values, cannot be rolled up, joined or filtered properly, and there are roughly 390 US metro areas. Replacing one with a junction object, seeded from the Census delineation file.

  • Picklists
  • Junction objects
  • Reporting
  • Data loading

Next step

Tell me where the operation hurts.

A 30-minute call. I will tell you whether Salesforce is the right answer for your shop — including when it is not.