"No such column <field> on entity 'Account'" error thrown when compiling or deploying Apex classes with different API versions
Trailblazer Community

"No such column <field> on entity 'Account'" error thrown when compiling or deploying Apex classes with different API versions

Last updated 2018-10-13 ·Reference W-2943792 ·Reported By 109 users

Fixed - Winter '19

Summary
An error occurs when compiling two or more classes together (either via Compile All Classes or Deployment) if one of the classes references Account entity fields not available in the API version selected by the compiler:

"No such column <field> on entity 'Account'. If you are attempting to use a custom field, be sure to append the '__c' after the custom field name. Please reference your WSDL or the describe call for the appropriate names."

The Apex compiler selects the API version specified by the first class it compiles. If the compiler selects an API version in which a compound field is unavailable, any attempt to access a compound field fails.

Repro
1- Create the following Apex class using API version 14.0
public class AccountNameClass {
public void accountAddressFields() {
List<Account> acc = [SELECT Id, Name FROM Account limit 1];
}
}

2- Create a second Apex class using API version 38.0
public class ShowBillingAddressClass {
public void ShowBillingAddress() {
List<Account> acc = [SELECT Id, Name, BillingAddress FROM Account limit 1];
}
}

3- On the "Apex Classes" page, click on the "Compile All Classes" option

4- Observe the following compilation message:

Compilation Complete
Compilation Errors found:
ShowBillingAddressClass: line 3, column 28: No such column 'BillingAddress' on entity 'Account'. If you are attempting to use a custom field, be sure to append the '__c' after the custom field name. Please reference your WSDL or the describe call for the appropriate names.

Note: Compound address fields, like BillingAddress, are available from API version 30

Workaround
The Apex compiler uses an elaborate process to select the API version to compile multiple Apex classes. The most reliable workaround for this issue is to avoid accessing compound fields. Instead, refer directly to component fields.

For example, the ShowBillingAddressClass in the example above can be fixed to use component fields instead of the BillingAddress compound field:

public class ShowBillingAddressClass {
public void ShowBillingAddress() {
List<Account> acc = [SELECT Id, Name, BillingStreet, BillingCity, BillingState,
BillingPostalCode,BillingCountry, BillingLatitude, BillingLongitude
FROM Account limit 1];
}
}

See the “Retrieving Compound Address Fields” section on this page for details.

Updates
6/1/2018 - Updated Subject, Summary and Workaround (with a more conservative approach), and added Internal Notes for the root cause of the problem.

Reported By (109)

Angela Zenner Rachel Zamora Blake Skidmore Anand Naik Pavel Klochkov Palak Patel Michael Butler Stacy Nguyen Priya Purushothaman Mike Combs Francisco Javier Bueno Vasquez Marco Tagnani Matt Bevins OAC Services Jim Royster Scott Bova Gary Casallas Lee Corey Gregg Cannella Wilson Kwok Megan Blanski Michael Rivera Richard DiNardo David Reed Stefan Gribi Eirik Skeid Gregory Butt Chris Feldhacker OAC Services Rachel Chand Andreas Nilsson Daniel Ballinger Ryan Sloan Winston Sucher Joe Pryor Pratha Ganesan Ann Manza-Geerts Mónica Lavandera Michelle Slayton Rob Bowman-pde3-dev Dan Walsh Jean-Hugues Blanc Adam Grossman Matt Proud Ramses Valencia Beatriz Esteves Dan Blackwell Niall Geraghty Russell Osman Thuy Le Eric Tang Shaan Kastuar Murugavel Dhandapani Charlotte Fleming Sidharth Chaturvedi Eileen Auton Jack Holdsworth Sian Bradley Marcel de Brauwer Mahesh Golla Himanshu Mattoo Guiseppe Hammer Craig Fuller Dorothy Smatana Ciro Rinaldi Marc Albaladejo Sans Svavar Árni Halldórsson Jean-Paul Antona Liz Ichihashi Salvador Méndez Sean Briceno Rick Farris Rick Farris Sonia Cruz Oró Sanjeev Goyal James Hadfield CRM Solutions Development Matt McGuire Ryan Marquardt TechnoMile Marco Sdino Quentin Tiercelin Fabien Michenaud Leslie Linard Developer Admin Andrew Downey Shalini Dixit everis SFA Brasil David Perez Santosh Kumar Piotr Skotnicki Yassine BOUARGOUB Pavan Hegde James Goerke Ross Freeman Stjepan Pavuna Jory Cohen Nigel Flear Dave Domagala Cody Maines Jeff Hube Matt Holloway Nelson Young SRINIZKUMAR KONAKANCHI Brenden Wells Liz Maxfield Brittany Williams Ryan Gardner Yasha Reddy

Is it Fixed?

AP0 AP3 AP4 AP5 AP6 AP7 AP8 AP9 AP10 AP11 AP12 AP13 AP14 AP15 AP16 AP17 AP18 AP19 AP20 AP21 AP22 AP24 AP25 AP26 AP27 AP28 CS1 CS2 CS4 CS5 CS6 CS7 CS8 CS9 CS10 CS109 CS108 CS107 CS106 CS105 CS102 CS101 CS100 CS115 CS119 CS110 CS117 CS114 CS113 CS112 CS111 CS11 CS116 CS123 CS122 CS121 CS126 CS127 CS129 CS128 CS125 CS124 CS137 CS138 CS133 CS132 CS14 CS148 CS142 CS159 CS152 CS151 CS15 CS162 CS167 CS166 CS16 CS169 CS165 CS160 CS173 CS17 CS172 CS170 CS171 CS174 CS18 CS189 CS194 CS192 CS193 CS190 CS191 CS199 CS197 CS19 CS198 CS196 CS195 CS20 CS209 CS200 CS202 CS201 CS203 CS21 CS219 CS218 CS217 CS216 CS215 CS214 CS213 CS212 CS211 CS210 CS22 CS220 CS23 CS234 CS24 CS25 CS26 CS27 CS28 CS29 CS31 CS32 CS33 CS34 CS35 CS36 CS37 CS40 CS41 CS42 CS43 CS44 CS45 CS47 CS53 CS57 CS58 CS59 CS60 CS61 CS62 CS63 CS64 CS65 CS66 CS67 CS68 CS69 CS72 CS73 CS74 CS75 CS76 CS77 CS78 CS79 CS80 CS81 CS84 CS86 CS87 CS88 CS89 CS90 CS91 CS92 CS94 CS95 CS96 CS97 CS98 CS99 EU16 EU17 EU18 EU19 EU25 EU26 EU27 EU28 EU29 EU30 EU31 EU32 EU33 EU34 EU35 EU36 EU37 EU38 EU39 EU40 EU41 EU42 EU43 EU44 EU45 EU46 EU47 EU48 NA104 NA107 NA109 NA100 NA101 NA103 NA102 NA105 NA119 NA116 NA110 NA118 NA112 NA111 NA115 NA114 NA113 NA117 NA125 NA124 NA122 NA120 NA126 NA127 NA123 NA129 NA121 NA128 NA138 NA134 NA133 NA136 NA135 NA132 NA131 NA130 NA137 NA139 NA140 NA142 NA141 NA149 NA146 NA147 NA148 NA154 NA158 NA159 NA153 NA151 NA155 NA152 NA150 NA156 NA161 NA163 NA167 NA160 NA166 NA165 NA169 NA164 NA168 NA162 NA172 NA170 NA174 NA171 NA173 NA196 NA207 NA204 NA206 NA208 NA209 NA21 NA218 NA214 NA217 NA215 NA212 NA213 NA210 NA65 NA70 NA71 NA75 NA80 NA81 NA82 NA83 NA84 NA85 NA89 NA90 NA91 NA92 NA93 NA94 NA95 NA96 NA97 NA98 NA99 UM1 UM2 UM3 UM4 UM5 UM6 UM7 UM8 UM9

Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.