• John James 40
  • 0 Points
  • Member since 2021

  • Chatter
  • 0
    Best Answers
  • 0
    Likes Received
  • 0
    Likes Given
  • 0
  • 3
Hi everyone,

I think that I found a bug in the screen flow component "reference" when referencing a filtered lookup. Salesforce support told me to ask here about it.

Here the official documentation : https://help.salesforce.com/articleView?id=flow_ref_elements_screencmp_lookup.htm&type=5

How to reproduce :
1 - create a new lookup field from contact to account "account2" without filtering
2 - create a simple screen flow with only a reference component using this new lookup
flow setup3 - test it : you find all your account
User-added image4 - add a filter on the lookup to display only the account of the contact
User-added image5 - nothing in the flow now :
User-added imageI have the same results if the filter is optional.

Did i missunderstand something ? Or is this a bug ?

I've a Login with salesforce functionality enabled in my application. When I generate a login oauth url which consists of app secret and ket and after sending a get request using browser It redirects me to a previously used cache instance url.

It should redirect to https://login.salesforce.com/?ec=302&startURL=%2{someurl}

but instead it's redirecting to https://myinstance.salesforce.com/?ec=302&startURL=%2{someurl} although I'm logged out of salesforce and this url only accepts my login credentials which are linked with my instance where as login.salesforce.com accepts anyone's login credentials.

if I use incognito window it works fine and I've even tested the oauth url using postman the response is a html file which has javascript function which redirects to login.salesforce.com/?ec=302&startURL=%2{someurl}
Is there anyway I can solve this issue or force my oauth url to redirect to login.salesforce instead of cached url.