Hi Lior Lavi,
The "Apex heap size too large" error occurs when too much data is being stored in memory during processing, you need to check the fields in base element having large number of data
Please refer following salesforce link for the your reference
Error 'Apex heap size too large' - Salesforce Help Help | Training | Salesforce
Hi Supriay, thank you for your reply.
The thing is, this window is supposed to to be paged to only show several items at the time and deal with large data sets with pagination.
Do you know how to set the column header of this window? Maybe if I'll limit it to the instance name of the base elements it will allow me to see them.
I changed the columns to only show Instance Name but I'm still getting the same error message:
Apex heap size too large: 14711483
Any ideas what else can I do?
I think it needs more detail investigation, please reach out to Remedyforce support team for this
2 of 2 people found this helpful
We opened a ticket because Application (CMDB Lookup) causes the same issue in our org. BMC opened a defect for this - 99224.
Unfortunately a fix is not in Patch 1 so I am hoping by patch 2 they have it fixed. Makes template management more difficult. (I am using salesforce layout to set application now)
Since summer19, we are no longer able to open base element object when we address it as a datasource via Excell; here also it looks as if the object has grown too large as we get a header too long message when selecting Base Element as data source in Excel. truncated error:
DataSource.Error: Web.Contents failed to get contents from 'https://telenet.my.salesforce.com/services/data/v29.0/query?q=SELECT Id,OwnerId,IsDeleted,Nam...
(431): Request Header Fields Too Large
Same rootcause ?
1 of 2 people found this helpful
So, here is the workaround I found to this issue. I hope it will be of some help to you until BMC fix this issue. Use this 'solution' at your own discretion
- Login to your Salesforce org as administrator.
- Open Developer Console.
- In the Query Editor search for your template ID by name with the following query: Select Id, Name from BMCServiceDesk__SYSTemplate__c WHERE Name like ' Your template's name goes here'. Copy your template's ID and paste it into Notepad so you'll have it available later.
- Use the following query to get your base element ID: Select ID from BMCServiceDesk__BMC_BaseElement__c Where Name = 'Your base element's name goes here'. Copy your base element's ID and paste it into Notepad so you'll have it available later.
- Use the following query in the Query Editor to get your template's existing field\value mapping. Paste the template ID you got from step 3: Select Id, BMCServiceDesk__fieldName__c, BMCServiceDesk__fieldValue__c, BMCServiceDesk__FKSYSTemplate__c, BMCServiceDesk__From_Import__c, BMCServiceDesk__FieldId__c from BMCServiceDesk__SYSTemplateFieldInfo__c WHERE BMCServiceDesk__FKSYSTemplate__c = 'Your template's ID goes here'
- Click on the Insert Row button and fill the following fields as follow:
- BMCServiceDesk__fieldName__c => Your lookup field's name.
- BMCServiceDesk__fieldValue__c = > Your base element's Name
- BMCServiceDesk__FKSYSTemplate__c => Your template's ID
- BMCServiceDesk__From_Import__c => Leave it as false
- BMCServiceDesk__FieldId__c => Your base element's ID
- Click on Save Rows button.
- Go to your template from Remedyforce Administration > Configure Application > Template and search for it by name.
- Check to see that your base element lookup field mapping was added.
- Create a record from the Remedyforce Console and validate that your lookup field in populated and the record is saved successfully.
If you are going to insert more then several templates at the time you might want to consider using a BI tool such as Pentacho Data integration to speed the process up.