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
Lorenzo StabileLorenzo Stabile 

flow and custom button

Since yesterday, i have a problem with a flow called by custom button.
The custom button contains the following url:

/s/flow/RiassegnaCaso?IdCaso={!Case.Id}&CurrentUserId={!$User.Id}

with 2 parameters, caseId and UserId.

It worked fine for over 6 months. Now the error message is:
"An unmanaged error occurred in the stream"
Lokesh KumarLokesh Kumar
I Hope your flow URL is correct. Remove the "/s/" at the beginning and try for more details follow this page 
https://trailhead.salesforce.com/en/content/learn/projects/flow_calculate/flow_calculate_implement 
Lorenzo StabileLorenzo Stabile
Hi Lokesh, thanks for your response. I have tried also with the url without /s but the flow doesn't work yet... :(
Lokesh KumarLokesh Kumar
Strange did you follow the trailhead article and make sure your flow is activated.
Lorenzo StabileLorenzo Stabile

Yes, it is very strange. 

I confirm you the flow is active and it is working fine till friday evening 
Lokesh KumarLokesh Kumar
This error you are getting via an email? If yes can you paste the email body
Lorenzo StabileLorenzo Stabile
The flow doesnt't receive the parameters passed by custom button:

RICERCA RAPIDA: Select_Current_User
Trova tutti i record User in cui:
Id Uguale a {!CurrentUserId} (null)
Memorizza questi record in {!CurrentUserVAR}.
Salva i valori di questi campi nella variabile: Id, Name
Risultato
No record found
RICERCA RAPIDA: Select_Case
Trova tutti i record Case in cui:
Id Uguale a {!IdCaso} ()
Memorizza questi record in {!CaseToUpdate}.
Salva i valori di questi campi nella variabile: Id, Informazioni_di_Risoluzion__c, Ultimo_Titolare_User__c, DettaglioMotivo__c, CaseNumber
Risultato
No record found.

The select queries for user and case failed.
Tad Aalgaard 3Tad Aalgaard 3
Not sure if this is the case, but with Summer 19 release they changed it so you have to have named parameters.

https://salesforce.stackexchange.com/questions/261119/lightning-navigation-is-not-working-after-summer-19-release

https://developer.salesforce.com/docs/atlas.en-us.lightning.meta/lightning/components_navigate_add_params.htm