Offline Symbol Table not indexing properly?

[Mark Levy]

I recently switched my connections over from the now deprecated connection method to OAuth.

Everything seemed fine with the new setup, but as I usually do I just created a new field in production and deployed it over to my sandbox org then tried refreshing the offline symbol table so that the field gets proper code completion and is colored purple instead of red in the IDE. The refresh seems to have completed successfully, but I am not getting the code completion or the proper coloring as if it is not properly indexed. I can save my file without errors, so the new field did deploy properly, it seems that it's just not properly being indexed.

What's going on here? Is there anything I can do to fix this? Not being able to update the Offline Symbol Table metadata on my orgs based on changes I make is going to be extremely frustrating.

To reiterate what I'm doing

• Using OAuth connections to Production and Sandbox
• Create a new field in Production inside of Salesforce
• Retrieve Metadata in Illuminated Cloud for Production
• Deploy the new field to Sandbox through Illuminated Cloud
• Generate Offline Symbol Table on the sandbox (have tried both Full and SObjects only)
• The new field does not show in code completion and is still colored red as if it doesn't exist. This persists even if I close and re-open the file I'm working with. It's showing as "Cannot resolve symbol", but the file can be saved properly without errors, so the field does exist on the sandbox server and was properly deployed.
• This seems to be new behavior, perhaps since I set up a new project and changed my connection to OAuth from the deprecated connection type
• There doesn't appear to be any error messages or issues from the Illuminated Cloud console.

Any assistance with this would be helpful. This seems like it might be a bug.

[Mark Levy]

I guess I should have also indicated I'm using Illuminated Cloud 2.3.8.5 with Intellij IDEA 2025.2.4 (Community Edition) 

IntelliJ details:
IntelliJ IDEA 2025.2.4 (Community Edition)
Build #IC-252.27397.103, built on October 23, 2025
Source revision: 9b31ba2c05b47
Runtime version: 21.0.8+1-b1038.73 amd64 (JCEF 122.1.9)

[Scott Wells]

My guess is that your profile does not have read authorization on the new field. Please see the documentation for the connection-level Ensure field read access setting here:

https://bitbucket.org/RoseSilverSoftware/illuminatedcloud/wiki/User_Guide/Configuring_Connections

Do not enable that option unless you're comfortable with IC updating your connection user's profile to read access to all fields! If that's not okay in these orgs -- and it's never okay in a production org and generally not okay in a shared sandbox, so probably not -- then you will need to add read authorization for these specific fields explicitly either via profile or permission set.

Once that's done, those fields will be included in the Salesforce metadata API responses and therefore the generated offline symbol table.

Please let me know if that doesn't make sense and/or doesn't work for you.

Regards,

Scott Wells

[Mark Levy]

That was it, thanks. I'll be sure to have that ticked in my connection config.

Second question:

I'm using a System Administrator account with my Illuminated Cloud OAuth connections. After I created the new field in Production, I didn't bother deploying an updated profile for the system admin between Production and my Sandbox (I only deployed the updated field) because I assume that the System Administrator account I'm using should have full access to all fields anyway. Is this not the case?

[Scott Wells]

I almost said this in my previous response, but in Salesforce, "System Administrator" is not "superuser". It's a standard profile that grants access to many things, but it doesn't automatically grant access to all SObject types and fields. Even users with that profile must be explicitly granted read access to SObject fields for them to appear in the key Metadata API  responses that IC uses to enumerate those fields during OST generation.

Regards,

Scott Wells

[Mark Levy]

Interesting. I've never run into any issues with not having access to fields before as a system admin so I just assumed it automatically got access to everything. This is good to know, thanks!