DEFECT: When executing a SOQL Query on Account that provides a list of Ids, unable to click on an Id value and get a detail of the record

[GoogleCodeExporter]

What steps will reproduce the problem?
1.  Execute a SOQL Query against the Account object that will result in a list 
of Ids

2.  Click on any Id in the list and you are taken to a screen that says the 
record does not exist

3.  This only occurs for the Account object, all other objects will take you to 
a detailed view of the record

What is the expected output? What do you see instead?

We are expecting to be taken to a more detailed view of that particular record

What version of Workbench are you using?

25.0.4

On what operating system and browser?

Lenovo T430, Windows 7, Google Chrome

(Validated that this is occuring on all users, some on Macs, some on PCs, using 
different browsers)

Please provide any additional information below.

Screen shots are attached.

Original issue reported on code.google.com by jay.greg...@veevasystems.com on 3 Dec 2012 at 4:17

Attachments:

• [MJN WorkBench Issue 12032012.docx](https://storage.googleapis.com/google-code-attachments/forceworkbench/issue-596/comment-0/MJN WorkBench Issue 12032012.docx)

[GoogleCodeExporter]

This seems like an issue on the Salesforce side with access to one or more of 
the related fields. Can you try selecting all the fields from the SOQL Query 
page for one of those accounts and see if there's any problem? If so, you can 
try adding the fields one at time to narrow it down to which one is causing the 
problem. Also, do you have Person Accounts enabled?

Original comment by ryan.bra...@gmail.com on 3 Dec 2012 at 4:39

[GoogleCodeExporter]

Thank you for the update, we will research this to see if it is related to a 
specific field or set of fields.  We do have Person Accounts enabled.

Original comment by jay.greg...@veevasystems.com on 3 Dec 2012 at 4:48

[GoogleCodeExporter]

Ryan - I have some updates for you.

1.  We are logged in as System Admin and validated that all Account fields are 
Visible to the System Admin Profile, so there should not be any configuration 
that would prevent visibility to the Account object based on individual fields.

2.  We have over 500 fields on the Account, so we cannot execute a query for 
all fields on the Account in a single SOQL statement.  What I did do was 
execute subsets and for all fields in the subsets, I was able to get the SOQL 
query to return results.  We are still unable to click on an individual record 
and see the details.

Please advise as to how to proceed from here.

Original comment by jay.greg...@veevasystems.com on 3 Dec 2012 at 6:33

[GoogleCodeExporter]

Ah, I see what the issue probably is. Since you have over 500 fields on 
Account, the SOQL that is being run behind the scenes when you click on the Id 
is failing, and returning the (incorrect) error message you are seeing. It's 
going to be a bit a work to break it into multiple queries, but I can at least 
return a reasonable error message for now so you know why its failing..

Original comment by ryan.bra...@gmail.com on 3 Dec 2012 at 10:55

[GoogleCodeExporter]

OK, thanks for the update.  One last bit of information, we did not experience 
this issue last week and all of the fields were still on the object then.  This 
issue has only occurred since last Thursday.

Original comment by jay.greg...@veevasystems.com on 3 Dec 2012 at 11:00

[GoogleCodeExporter]

Hmm, interesting, nothing has changed with Workbench in the last week either, 
so I'm thinking something with Salesforce perhaps? I just deployed a change to 
add some logging to the query that gets run behind the scenes so I can get an 
idea of what's going on. Can you try again a couple times to generate some log 
data?

Original comment by ryan.bra...@gmail.com on 3 Dec 2012 at 11:47

[GoogleCodeExporter]

Thanks, Ryan!  I just logged in using proserv@mjn.com and generated 4 separate 
queries on the Account object, and then for each result set, randomly selected 
an ID value and clicked on it, and each time the error was generated.  
Hopefully that will give you some data to review.  I am going to be logging off 
now, I will check in tomorrow morning around 9 am Central Time to see if you 
were able to get any better information from these results.

Original comment by jay.greg...@veevasystems.com on 3 Dec 2012 at 11:55

[GoogleCodeExporter]

Thank! I checked the logs and confirmed the error happening behind the scenes 
is "MALFORMED_QUERY: SOQL statements can not be longer than 10000 characters." 
So, the question is if anything happened on the Salesforce side to make this 
start happening now. Before I start investigating that, are you sure nothing 
changed on your object to add more fields or even access changes that allow you 
to see more fields than before? Another thing you can do is increase the char 
limit on your org to 20000 chars. You should be able to contact Salesforce 
Support and have them increase it for your org.

Original comment by ryan.bra...@gmail.com on 4 Dec 2012 at 12:03

[GoogleCodeExporter]

Ryan, thanks for the update. FYI, we logged a case with Veeva Support to 
request the increase in the SOQL Query limit to 20,000 characters.

We did an archive history on the fields for Account and the number of fields 
did not change from last week to this week, and while the FLS did change for 
some profiles, it did not change for the profiles accessing Workbench, 
specifically it did not change for the System Admin profile.

Let me know if there is anything more you need to investigate.

Original comment by jay.greg...@veevasystems.com on 4 Dec 2012 at 5:58

[GoogleCodeExporter]

**NOTICE**
All issues for Workbench in the Google Code project "forceworkbench" have been 
migrated to the GitHub project "ryanbrainard/forceworkbench":

https://github.com/ryanbrainard/forceworkbench

Issue numbers have been retained between the two services so migrated issues 
can be easily found on GitHub (e.g. Issue #123 on Google Code is still Issue 
#123 on GitHub). If you wish to receive future updates about an open issue, you 
will need to re-follow the issue on GitHub.

Original comment by ryan.bra...@gmail.com on 27 Jan 2013 at 5:30

• Changed state: Migrated