@jessealtman json.deserialize(string). Docs here: http://t.co/KxDoChRMDB #askforce
— Mike Jones (@veterankamikaze) April 11, 2014
via Twitter
It's a thing. Sometimes there's stuff.
@jessealtman json.deserialize(string). Docs here: http://t.co/KxDoChRMDB #askforce
— Mike Jones (@veterankamikaze) April 11, 2014
via Twitter
@dseli That code is a simpler version of what I'm doing. Go us for finding a Salesforce bug!
— Mike Jones (@veterankamikaze) April 9, 2014
via Twitter
@dseli This was added to the Known Issues list: https://t.co/rTMlRc5thC
— Mike Jones (@veterankamikaze) April 9, 2014
via Twitter
@JessieGrenfell Figured out my issue a few minutes ago. Needed to format DT as string but was getting some goofy query results.
— Mike Jones (@veterankamikaze) April 7, 2014
via Twitter
@dseli Same here. I'm resisting bumping up the API version of the class that causes the problem in my org. Want SF to fix this obv bug.
— Mike Jones (@veterankamikaze) April 7, 2014
via Twitter
@dseli Yep, my experience as well. Seems to be a lower API version seeing something it shouldn't be able to see.
— Mike Jones (@veterankamikaze) April 7, 2014
via Twitter
@dseli Still broken for me and very slow progress on my case. Have gotten my account rep involved.
— Mike Jones (@veterankamikaze) April 7, 2014
via Twitter
Anyone have time for a quick SOQL datetime question? Banging my head against a wall… #askforce #forcedotcom
— Mike Jones (@veterankamikaze) April 7, 2014
via Twitter
@hammnick That's missing Address and Location, hence my last tweet. I wonder what else is missing.
— Mike Jones (@veterankamikaze) March 26, 2014
via Twitter
@hammnick Thanks for that. Sort of related: Any way to find all of the schema.displaytype enums?
— Mike Jones (@veterankamikaze) March 26, 2014
via Twitter
@salesforcedocs Makes me wonder if there are other items that aren't documented…?
— Mike Jones (@veterankamikaze) March 26, 2014
via Twitter
@salesforcedocs The Apex Code Developer's Guide seems to be missing two displaytype enums. Address and Location types are not documented.
— Mike Jones (@veterankamikaze) March 26, 2014
via Twitter
@salesforce I think there is some missing information in the Apex Developers guide. Who can I report this to? #askforce #forcedotcom
— Mike Jones (@veterankamikaze) March 26, 2014
via Twitter
@horicentweets Was afraid of that. Want to raise an exception to the calling code, but log that it happened in mine. #askforce #forcedotcom
— Mike Jones (@veterankamikaze) March 26, 2014
via Twitter
Any clever way to react to data condition by doing DML, then throw a custom exception? #askforce #forcedotcom
— Mike Jones (@veterankamikaze) March 26, 2014
via Twitter
@JessieGrenfell @forcedotcom Yeah, have fun. I’ve been chasing down ISE w/ support for a few weeks now…
— Mike Jones (@veterankamikaze) March 25, 2014
via Twitter
@JessieGrenfell @forcedotcom Be persistent. Internal Salesforce Error is not your fault. You aren’t asking for dev support. #askforce
— Mike Jones (@veterankamikaze) March 25, 2014
via Twitter
If your batches fail and you know it, clap your hands. *clap clap* #forcedotcom #isitbeerthirtyyet?
— Mike Jones (@veterankamikaze) March 18, 2014
via Twitter
@FitbitSupport Will the Force still be supported for users who choose to not participate in the recall?
— Mike Jones (@veterankamikaze) March 13, 2014
via Twitter
@andyboettcher Thanks for this write up. Passing it along to a coworker who was fighting this a few weeks ago and gave up.
— Mike Jones (@veterankamikaze) March 11, 2014
via Twitter