• Richard DiNardo 6
  • 15 Points
  • Member since 2015

  • Chatter
  • 0
    Best Answers
  • 0
    Likes Received
  • 1
    Likes Given
  • 0
  • 6
Hi Guys,

Can any one help me how to hide the probability standard field in the opportunity page layot. As i already have a other custom filed that says probabilty. Is there any way that i can hide it form the page lay out.

Thanks in advance,
I am fairly new to Apex Development and am trying to debug some code developed by a senior level developer.
The code is a controller extension that errors with a SOQL limit without completing so the page is not completed.

I added system.debug statements to some of the methods in the code, turned on debug for my user and many different levels of debug but my system.debug statements fail to appear in the debug logs.  Based on other detailed entries in the debug log I have confirmed that the code where I've added system.debug is being executed.

Any suggestions?   I'm probably making a very simple/common beginner mistake.

  • March 10, 2014
  • Like
  • 0
We want to add hundreds of images in visualforce page(like images in online shopping) and the user of the application should be upload/delete the image by himself dynamically?


Thanks in Advance,
Naga Kiran Kumar K

This may not be the appropriate place to ask this question but I don't know if there is a discussion board about the force.com IDE. The problem I'm having is that the force.com IDE I just downloaded and installed is missing the Run Tests option. The docs I find about running tests all say to right click on a test class and then go to Force.com > Run Tests. Unfortunately the Run Tests option is missing.


Does have any suggestions for fixing this problem?


Thank you

is there a way to convert a list of sobjects into a string?  I don't really care about the format, just that the field values can be string searched. Something like this:



List<sobject> pparcels = database.query('select ...');
String relatedMatches = pparcels.toString(); //toString doesn't exist
if (relatedMatches.indexOf(affectedIds[i]) > -1) {



  • June 22, 2010
  • Like
  • 0

I have installed an application called CaseHistory from appExchange and wanted to modify the relevant VisualForce page - CaseHistory.page.


I attempted to use the title attribute of the <apex:page> tag as follows:

<apex:page showHeader="false" controller="CaseHistoryController" title="Case: {!aCase.CaseNumber}">


However, I keep seeing the title as "Page Editor - /apex/CaseHistory". I changed my user setting to NOT be in Developer mode but I still don't see the page title changed to what I was trying to set in the code above (Case: caseNumber).


Any ideas on how to resolve this?


Thanks in advance,


Hi all,

I'm evaluating pros and cons for building an integration with Salesforce on Force.com platform. Since the pros don't need to be commented on, I'll just ask about what some developers consider as cons. I came across this SO question: http://stackoverflow.com/questions/1664503/disadvantages-of-the-force-com-platform What part of this can you confirm as true, and what not? The question is closed because of the format, but it'd be great if someone could provide concrete answers to it (when you google for disadvantages you get this at the top). I'll copy and paste some of the mentioned disadvantages for easier referencing:
  1. Apex is a proprietary language. Other than the foce.com Eclipse plugin, there's little to no tooling available such as refactoring, code analysis, etc.
  2. Apex was modeled on Java 5, which is considered to be lagging behind other languages, and without tooling (see #1), can be quite cumbersome.
  3. Deployment is still fairly manual with lots of gotchas and manual steps. This situation is slowly improving over time, but you'll be disappointed if you're used to having automated deployments.
  4. Apex lacks packages/namespaces. All of your classes, interfaces, etc. live in one folder on the server. This makes code much less organized and class/interface names necessarily long to avoid name clashes and to provide context. This is one of my biggest complaints, and I would not freely choose to build on force.com for this reason alone.
  5. The "force.com IDE", aka force.com eclipse plugin, is incredibly slow. Saving any file, whether it be a class file, text file, etc., usually takes at least 5 seconds and sometimes up to 30 seconds depending on how many objects, data types, class files, etc. are in your org. Saving is also a blocking action, requiring not only compilation, but a full sync of your local project with the server. Orders of magnitude slower than Java or .NET.
  6. The online developer community does not seem very healthy. I've noticed lots of forum posts go unanswered or unsolved. I think this may have something to do with the forum software salesforce.com uses, which seems to suck pretty hard.
  7. The data access DSL in Apex leaves a lot to be desired. It's not even remotely competitive with the likes of (N)Hibernate, JPA, etc.
  8. Developing an app on Apex/VisualForce is an exercise in governor limits engineering. Easily half of programmer time is spent trying to optimize to avoid the numerous governor limits and other gotchas like visualforce view state limits. It could be argued that if you write efficient code to begin with you won't have this problem, which is true to an extent. However there are many times that you have valid reasons to make more than x queries in a session, or loop through more than x records, etc.
  9. The save->compile->run cycle is extremely slow, esp. when it involves zipping and uploading the entire static resource bundle just to do something like test a minor css or javascript change.
  10. In general, the pain of a young, fledgling platform without the benefits of it being open source. You have no way to validate and/or fix bugs in the platform. They say to post it to their IdeaExchange. Yeah, good luck with that.
  11. You can't package up your app and deliver it to users without significant user intervention and configuration on the part of the administrator of the org.
  12. THERE IS NO DEBUGGER! If you want to debug, it's literally debug by system.debug statements. This is probably the biggest problem I've found
  13. Even tho the language is java based, it's not java. You can't import any external packages or libraries. Also the base libraries that are available are severely limited so we've found ourselves implementing a bunch of stuff externally and then exposing those bits as services that are called by force.com
  14. There is no mention anywhere in even the most deep-dark technical references of the common errors, or even the limitations of a given api or feature