function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
Manos SpanoudakisManos Spanoudakis 

Critical Update and URLFOR in Custom buttons

hi all, 

 

Since the activation of a critical update (Block custom links or custom buttons that contain invalid URLs) we are not able to use any Custom Button using the URLFOR function ! 

 

Buttons are still in page layouts but yet inactive ! 

 

For example this (List button type URL) 

 

{!URLFOR($Action.Account.New,Opportunity.Id,[retURL="Account.Id"])} 

 

doesn't work ! 

 

Any hints ? 

 

Thanxxx

logontokartiklogontokartik
Looks like there is some sort of issue if we are using Params in the URLFOR, causing the Custom Link to not work. Try removing the [retURL] part and try, it should work. Maybe we need to open a case with Salesforce on Param issue though
Manos SpanoudakisManos Spanoudakis

Exactly ! Works without problems when the [params] is removed ! Already opened a case with support but still not any useful feedback...

 

 
Manos SpanoudakisManos Spanoudakis

do you also have the same issue ?
logontokartiklogontokartik
Yes. looks like Activating the Critical Update is causing the issue.
Manos SpanoudakisManos Spanoudakis

Salesforce plans to kill this functionality ?? 

this is very critical  for all !!

 

All the Custom Buttons using URLFOR with parameters will STOP TO WORK!!!

 

What do you think is this a big fail or not ??

 

UPDATE: probably a bug salesforce is now investigating :)
Manos SpanoudakisManos Spanoudakis

It's a BUG so either deactivate the Critical Update or ignore the strange behavior 
benderguybenderguy

It isn't on the known issue list yet. I have opened a case with SF Partner Support on this (# 08809750).

 

 

Peter Bender
Salesforce services & solutions for high performing nonprofits
(800) 918-2917  | Get a free consultation with nonprofit experts
Manos SpanoudakisManos Spanoudakis

Hi Peter,

 

We didn't get far when we tried support. However, check this twitter conversation ;-) should be now resolved I didn't have the time to check yet...

 

https://twitter.com/shannonsans/status/304734183459262464
Shannon HaleShannon Hale

Sorry everyone, we introduced a bug with parameter parsing in URLFOR() in Spring '13.

 

My team put out a fix in patch this week and it should now be working.

 

Shannon Hale

Senior Product Manager, Declarative Apps

Salesforce.com