@andyboettcher bah! Link vomited: http://t.co/Zq0lqnyVeQ
— Mike Jones (@veterankamikaze) March 10, 2014
via Twitter
It's a thing. Sometimes there's stuff.
@andyboettcher bah! Link vomited: http://t.co/Zq0lqnyVeQ
— Mike Jones (@veterankamikaze) March 10, 2014
via Twitter
@andyboettcher selective queries per this: http://t.co/Zq0lqnyVeQ #askforce
— Mike Jones (@veterankamikaze) March 10, 2014
via Twitter
@andyboettcher NA10 instance, production. Reading up on selective queries. ~84000 rows, query returns 54. #askforce
— Mike Jones (@veterankamikaze) March 10, 2014
via Twitter
@CarolEnLaNube That’s why I was thinking, but the query only returns 54 records.
— Mike Jones (@veterankamikaze) March 10, 2014
via Twitter
SQLException [common.exception.SfdcSqlException: ORA-01013: user requested cancel of current operation #forcedotcom #askforce (2 of 2)
— Mike Jones (@veterankamikaze) March 10, 2014
via Twitter
.@salesforce is killing my batch jobs with some screwy message. #askforce #forcedotcom (1 of 2)
— Mike Jones (@veterankamikaze) March 10, 2014
via Twitter
@michaellorg Not that I know of but it would be pretty easy with something like http://t.co/sHHAduogAc #askforce
— Mike Jones (@veterankamikaze) March 7, 2014
via Twitter
@Kwongerific Hmm… looks like I’ll have to go dig around through the meta data API to find this stuff.
— Mike Jones (@veterankamikaze) March 7, 2014
via Twitter
@Kwongerific Actually, can you clarify “go through each record type”? Do you mean manually?
— Mike Jones (@veterankamikaze) March 7, 2014
via Twitter
@Kwongerific Oof. Gross. I was hoping for something akin to CaseStatus object where I can tell if a particular status is closed or not.
— Mike Jones (@veterankamikaze) March 7, 2014
via Twitter
@veterankamikaze To clarify that last one: Want to find records that are not in a valid status for recordtype. #askforce #forcedotcom
— Mike Jones (@veterankamikaze) March 7, 2014
via Twitter
Any way of knowing which pick list values are available for which record types? Specifically Case status? #askforce #forcedotcom
— Mike Jones (@veterankamikaze) March 7, 2014
via Twitter
@Kwongerific I'm generally OK with it unless there are a boatload of posts from one person all at the same time.
— Mike Jones (@veterankamikaze) March 5, 2014
via Twitter
That thing when your emergency deploy takes 40 minutes… #forcedotcom
— Mike Jones (@veterankamikaze) March 3, 2014
via Twitter
@salesforce Can I get some help with a case? Have multiple unit tests failing with ‘Internal Salesforce Error’ since #spring14 hit sandbox.
— Mike Jones (@veterankamikaze) February 28, 2014
via Twitter
@veterankamikaze Spoke too soon. Errors still occur. #askforce #forcedotcom #Spring14
— Mike Jones (@veterankamikaze) February 24, 2014
via Twitter
@veterankamikaze Seems to be resolved if I lower the API version of the classes in question to v28 (was v29). #askforce #forcedotcom
— Mike Jones (@veterankamikaze) February 24, 2014
via Twitter
Wonderful. Internal Salesforce Errors while running new unit tests for a new class. #Spring14 being really touchy for anyone else? #askforce
— Mike Jones (@veterankamikaze) February 24, 2014
via Twitter
Lovely. #Spring14 has broken some of my code. "ColumnType.Location is not available in API version”. #askforce #forcedotcom
— Mike Jones (@veterankamikaze) February 17, 2014
via Twitter
Anyone see this in Eclipse? “location Not a valid enumeration for type: class com.sforce.soap.partner.wsc.SoapType” #Spring14
— Mike Jones (@veterankamikaze) February 10, 2014
via Twitter