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
3 - test it : you find all your account
4 - add a filter on the lookup to display only the account of the contact
5 - nothing in the flow now :
I have the same results if the filter is optional.

Did i missunderstand something ? Or is this a bug ?

Hi everyone,

I work for an ISV and sometimes the customer make some data modification as I'm working on his org.

All modification are written as done by the user I'm logged with so it's impossible afterwards to know if I did the modification or him.

Is there any way through SOQL to retrieve who really did the modificaition ?

I use this kind of SOQL from this article (https://developer.salesforce.com/docs/atlas.en-us.soql_sosl.meta/soql_sosl/sforce_api_calls_soql_relationships_query_hist.htm) :

SELECT OldValue, NewValue, Parent.Id, Parent.name, Parent.customfield__c 
FROM foo__history

I'm looking for, if it's possible, the right field to put in select to retrive this information.

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
3 - test it : you find all your account
4 - add a filter on the lookup to display only the account of the contact
5 - nothing in the flow now :
I have the same results if the filter is optional.

Did i missunderstand something ? Or is this a bug ?

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
3 - test it : you find all your account
4 - add a filter on the lookup to display only the account of the contact
5 - nothing in the flow now :
I have the same results if the filter is optional.

Did i missunderstand something ? Or is this a bug ?

Hi everyone,

I work for an ISV and sometimes the customer make some data modification as I'm working on his org.

All modification are written as done by the user I'm logged with so it's impossible afterwards to know if I did the modification or him.

Is there any way through SOQL to retrieve who really did the modificaition ?

I use this kind of SOQL from this article (https://developer.salesforce.com/docs/atlas.en-us.soql_sosl.meta/soql_sosl/sforce_api_calls_soql_relationships_query_hist.htm) :

SELECT OldValue, NewValue, Parent.Id, Parent.name, Parent.customfield__c 
FROM foo__history

I'm looking for, if it's possible, the right field to put in select to retrive this information.

 

I am getting 'Too many script statements: 10201'

 Governor Limit error when submitting ~100 or more updates at a time via the list view. 

 

When using the list view,  does it update in batch?  If so, according to the docs in the case of 100 records I should have 10,000 + (100*200) = 30,000 script statements allowed not 10200.  

 

If it's not updating in batch then why doesn't it happen when doing 1-50 updates?

 

Additional Details:

 All the updates performed were not data changes,  just a hit to have the trigger executed

 This is not an issue when doing a single update via the edit.

 or  less then 50 via the list view.

 or 200 via the API.

I Also updated all record (+250k) via the API wo/ any gov limit errors, This proves its not caused by a differences in the records data causing difference logic to be applied.

 

Tom