Error when generating offline metadata

[William Grymuza]

Hi Scott. 

I had a problem with my "Generate Offline Symbol Table" functionality. (Full, not just SObjects).

I was using parallel processing to make it quicker and it sometimes worked, sometimes partially worked, sometimes just wouldn't work. 

The symptoms were: red all over the code. 

Known classes, references, etc were all missing. 

I disabled parallel processing and tried again, this time I actually got an error back:

Maximum Number of Child Elements limit (50000) Exceeded:

This happened when it was generating "tooling sobject stuff" (I'm unsure the exact step) and I'm able to replicate this consistently.

That basically leaves me with some fields not being recognised, some classes missing altogether (despite the field and class in question being part of the project). 

The field is NOT included in downloaded object when I try to pull the data from source: 

despite it being part of the project: 

I've tried refreshing and retrieving metadata, That doesn't resolve the issue. 

For the reference: I'm working on big org, with hundreds of objects and hundreds of fields on some of those objects. 

Sometimes it leaves me with none of the fields being recognised as valid (therefore all highlighted as red), including standard fields. 

The error doesn't manifest itself when parallel processing is enabled on the connection settings:

This issue is happening (randomly) on all sandboxes, including brand new just refreshed, as well as production org. 

Is this a SF limit, or IC2?

Additionally - I also noticed that the following methos are not being recognised from Location datatype:

This is from field on the object where type is 'GeoLocation':

Unsure if those are related to each other, but though I'd mention this as well. 

Can you advise please? 

Thanks, 

William

[Scott]

Hi. Please see this:

https://groups.google.com/a/illuminatedcloud.com/g/qanda/c/2tDjp9q6wGI/m/W9co-Gb3AQAJ

You should be able to use parallel processing in all situations now. I should just remove that option as there's no reason (to my knowledge) to disable it, and things are WAY slower without it.

Regards,

Scott Wells

[Scott]

Sorry, replied too quickly. The unresolved fields in the OST are likely due to insufficient authorization for your connection user. Please see the documentation for Ensure field read access here:

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

If you're not working against a dedicated DE org or scratch org, you won't likely want to enable that option for the connection, but you will need to authorize your user for the missing fields for them to be included in the Salesforce API response and therefore the resulting OST.

Please let me know if you still have issues after applying these changes.

Regards,

Scott Wells