Year: 2010 (Page 8 of 8)

What is the change?
In Spring ‘10, when you create a new custom object, the “Read,” “Create,” “Edit,” “Delete,” “View All,” and “Modify All” permissions for that object will be disabled by default. After the Spring ’10 release, you must specify which users should get access to custom objects.

Note: You can only change the object permissions for custom profiles, not standard profiles. As a result, users with standard profiles (except System Administrator) will not be able to access custom objects created after the Spring ’10 release.

How will this change impact me?
If you have users assigned to standard profiles, clone these profiles and reassign your users to the newly created profiles. Then, when you create a new custom object, you will edit the user profiles to enable object permissions. Additionally, you can use enhanced profile management to edit multiple profiles at once.

Note: For custom objects created before the Spring ’10 release, access to these objects will not change. Therefore, standard profiles will continue to have access to custom objects created prior to the Spring ’10 release.

When is this change taking place?
This change will be made with the Spring ‘10 release. Please check http://trust.salesforce.com/trust/status/#maint to understand when your instance will be upgraded.

Source : http://www.interactiveties.com/b_remove_scrolls.php

Many new salesforce.com AJAX developers ask me how I am able to build my sControls into a frame and get the sizing setup in such a manner to prevent scrollbars. Over the years I’ve tried many different JavaScript functions but found that one works better than any I’ve seen.

For those reading this that might be unfamiliar with what I’m referring too I’ve included a screenshot.
In some instances an AJAX developer may want to build a sControl into salesforce.com whereby the sControl is embedded into the page. Basically there are tabs at the top and the navigation bar on the left-hand side with the sControl on the right-hand side.

When the web tab containing a sControl is setup through the Salesforce.com user interface the developer is allowed to dictate the size of the frame in which the sControl gets loaded. In most cases these new developers will simply alter that frame size to account for the largest height that may occur in the sControl. However, the script that I will eventually share with you will allow these developers to now ignore this pixel height setting and resize the frame dynamically.

I started using the script a year or two ago and a few months ago I altered it a bit because I was still getting scrollbars in Firefox. I found that the scrollbars didn’t always occur but I wanted to account for the percentages and try to eliminate them in entirely. Therefore, I decided to add a line where I determine if the browser is Firefox and then add 10 pixels to the adjusted frame height. I found that this truly eliminates the vertical scrollbars in almost 100% of the instances where I’ve used this script.

//resizes the frame holding the sControl to make up for odd dimensions
function resizeFrame()
{
var sframe = parent.document.getElementById("itarget"); //get id of iframe from parent
if (navigator.userAgent.indexOf("Firefox") != -1)
{ //if Firefox
var nHeight = document.body.scrollHeight+10; //add ten pixels to height of sControl frame
}
else
{ //otherwise
var nHeight = document.body.scrollHeight; //use the returned height of sControl frame
}
sframe.style.height = nHeight+"px"; //set the frame height to correspond to the content
}

And it can be called using this line:
resizeFrame(); //calls function from above

I hope you find this useful or can tweak it to meet your needs.,

Requirement

I’d like to create a button on Opportunities that does several things:
1.) Closes the Opportunity (Stage = Closed Lost)
2.) Makes a custom field have a specific value (Opportunity Lost Reason = “Wrong/Bad Number”

Solution:
Here’s the URL behind the button:

/{!Opportunity.Id}/e?retURL={!Opportunity.Id}&opp11=”Closed Lost”&00N80000002eg5T=”Wrong/Bad Number”&save=x

Where

00N80000002eg5T is the ID of the “Opportuntiey Lost Reason” custom field!
opp11 is the SF field name for Stage standard field in the layout.
save=x will automatically save the record after the changes are made.