Hey there - this one goes out to the Salesforce devs that may be listening.  

We have a visualforce page that was written about a year ago which is basically a custom report exporting as PDF.   Suddenly, without any changes in page code, the page stopped working and is giving the dreaded 'internal server error' message withthe following code:

Error ID: 1183247688-671 (1462077656)

All the debug logs say that the page call succeeded and there is no indication of any error.  This has been submitted to support as #02660758. 

What can we do to try and understand what is actually causing this error??  Is there any way to get more information on the error detail?

Many Thanks! 

Hello - would like to get the community's opinion/input on this:

We are performing an implementation  where the user is requiring a large set of individual 'roll-up' fields on the Opportunity (and other) objects.  These fields are essentially summaries for fields on other objects that are related to the opportunity.  These objects are not master-detail, and actually may not be directly related (could be 2 objects away, for example).  After refactoring the object design as much as possible, it is not possible to bring things together nicely into master-detail relationships to use the Salesforce 'Roll-up Summary fields'.  (although Salesforce allowing 3-deep master detail relationships would go a long way)

So, when we decided how to implement this, we come up with the following two options: 

1)  Create 'mini', single-field Visualforce pages for each of these summaries that can be embedded into the Standard Opportunity page layout.  These pages would be for the standard 'Opportunity' controller but have a controller extension, lets call it 'oppFieldCalcs'.  Create the apex class 'oppFieldCalcs' to generate the values of each of these 'mini' visalforce pages/fields using SOQL statements, etc. as normal.  When the page loads, it runs all that code and builds the values for the fields.  Essentially, the 'pull' model of obtaining these summary fields.

or

2) Create fields on the Opportunity object to act as placeholders for the summary values, then put logic in in insert/update/delete triggers for each of the 'related' objects that will  update those placeholder field values incrementally as the related object records are manipulated. (i.e. when a new related object record is created, summary field count value is 'current value +1', etc.)  This is essentially the 'push' model of obtaining these summary fields. 

What does the expert community think about this? 

Currently, we are proceeding with option 1.  The visualforce embedding seems to work fine, although the layout restriction of harcoded page heights and delay-processed iframes  feels a little kludgey.  Plus, the user feels that the application is 'slower' since the page takes longer to grab all the extra field values.     

On the other hand, this way the code is all in one place rather than distributed amongst a variety of triggers on disparate objects. It seems more manageable and resilient to change this way. Even though the trigger-based 'push' model makes the page layouts very clean for the user.

Many Thanks for your input.

<apex:dataTable value="{!opportunity.OpportunityLineItems}" var="Item" width="675" rules="all" cellPadding="6" styleClass="data" columnClasses="info_bottom_1, info_bottom_2, info_bottom_3, info_bottom_4">
            <apex:column>
                 <apex:outputField value="{!Item.TotalPrice}"/>
            </apex:column>
   </apex:dataTable>

USD 47,250.00

Is there any one who knows how to use setContentType for Meeting Invites when we send an Email with EmailFileAttachment.

Much appreciated

Hi,

I am having difficulty with attempting to create a new custom object. I have a valid connection etc. (In this case to a sandbox).

The login credentials have sysadmin rights.

The error I get is "Unable to determine type mapping for type CustomObject.  Type is illegal here."

I have no idea what the issue is. 

I have posted the SOAP request below (header removed).

<?xml version="1.0" encoding="utf-8"?> <SOAP-ENV:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP-ENV:Header> {Header removed} </SOAP-ENV:Header> <SOAP-ENV:Body xmlns="http://tempuri.org/"> <create xmlns="http://soap.sforce.com/2006/04/metadata"> <metadata xsi:type="ns1:CustomObject"> <fullName>MYOB__c</fullName> <customSettingsType>List</customSettingsType> <deploymentStatus>Deployed</deploymentStatus> <description>This is a test Object created using the Metadata API.</description> <enableActivities>true</enableActivities> <fields> <fullName>MyField__c</fullName> <description>This is a description of a custom field.</description> <formulaTreatBlanksAs>BlankAsBlank</formulaTreatBlanksAs> <label>My Custom Field</label> <maskChar>asterisk</maskChar> <maskType>all</maskType> <picklist> <sorted>false</sorted> </picklist> <summaryOperation>count</summaryOperation> <type>Text</type> </fields> <gender>Neuter</gender> <label>Mind Your Own Business</label> <nameField> <formulaTreatBlanksAs>BlankAsBlank</formulaTreatBlanksAs> <maskChar>asterisk</maskChar> <maskType>all</maskType> <picklist> <sorted>false</sorted> </picklist> <summaryOperation>count</summaryOperation> <type>AutoNumber</type> </nameField> <pluralLabel>Mind Your Own Businesses</pluralLabel> <searchLayouts /> <sharingModel>ReadWrite</sharingModel> <startsWith>Consonant</startsWith> </metadata> </create> </SOAP-ENV:Body> </SOAP-ENV:Envelope>

 Any help is appreciated.

Hey there - this one goes out to the Salesforce devs that may be listening.  

We have a visualforce page that was written about a year ago which is basically a custom report exporting as PDF.   Suddenly, without any changes in page code, the page stopped working and is giving the dreaded 'internal server error' message withthe following code:

Error ID: 1183247688-671 (1462077656)

All the debug logs say that the page call succeeded and there is no indication of any error.  This has been submitted to support as #02660758. 

What can we do to try and understand what is actually causing this error??  Is there any way to get more information on the error detail?

Many Thanks! 

Hello - would like to get the community's opinion/input on this:

We are performing an implementation  where the user is requiring a large set of individual 'roll-up' fields on the Opportunity (and other) objects.  These fields are essentially summaries for fields on other objects that are related to the opportunity.  These objects are not master-detail, and actually may not be directly related (could be 2 objects away, for example).  After refactoring the object design as much as possible, it is not possible to bring things together nicely into master-detail relationships to use the Salesforce 'Roll-up Summary fields'.  (although Salesforce allowing 3-deep master detail relationships would go a long way)

So, when we decided how to implement this, we come up with the following two options: 

1)  Create 'mini', single-field Visualforce pages for each of these summaries that can be embedded into the Standard Opportunity page layout.  These pages would be for the standard 'Opportunity' controller but have a controller extension, lets call it 'oppFieldCalcs'.  Create the apex class 'oppFieldCalcs' to generate the values of each of these 'mini' visalforce pages/fields using SOQL statements, etc. as normal.  When the page loads, it runs all that code and builds the values for the fields.  Essentially, the 'pull' model of obtaining these summary fields.

or

2) Create fields on the Opportunity object to act as placeholders for the summary values, then put logic in in insert/update/delete triggers for each of the 'related' objects that will  update those placeholder field values incrementally as the related object records are manipulated. (i.e. when a new related object record is created, summary field count value is 'current value +1', etc.)  This is essentially the 'push' model of obtaining these summary fields. 

What does the expert community think about this? 

Currently, we are proceeding with option 1.  The visualforce embedding seems to work fine, although the layout restriction of harcoded page heights and delay-processed iframes  feels a little kludgey.  Plus, the user feels that the application is 'slower' since the page takes longer to grab all the extra field values.     

On the other hand, this way the code is all in one place rather than distributed amongst a variety of triggers on disparate objects. It seems more manageable and resilient to change this way. Even though the trigger-based 'push' model makes the page layouts very clean for the user.

Many Thanks for your input.

You can see that we created an html Span, and had the style returned from the row of data.  This way the data object can completely customize the style returned. 

----------------------------------------------------------------------------

However, you can see that there are 2 different attributes, and there is that "grp.obj.name".  The reason for this is that the SObject that we use does not and should not contain "Display code".  In the "Model View Controller" model, that means that the SObject is the Model, and the style generation is the View.  

We solve this problem by creating a SObject display object that contains the style customization logic. 

public class DrugGroupDisp
{
    private drug_group__c obj;
    public drug_group__c getObj()
    {
        return obj;
    }
    public void setObj(drug_group__c s)
    {
        obj = s;
    }

   public String getNameStyle()  

  {
        if (some condition} return 'color: red';

       return 'color: green';

    }

                   
    public void Setup(drug_group__c o)
    {
        obj = o;
    }
}

By having a direct reference to the original SObject, we can get access to all of its attributes, and then if needed we can made modifications and save.

the display object gives us a row level wrapper that can provide customizations that the Visual Force Page can use for rendering.

----------------------------------------------------------------------------

Here is how we load the display object:

public List<DrugGroupDisp> getGroups()
    {
         if (groups == null)
         {
             groups = new List<DrugGroupDisp>(); 
            
             for(drug_group__c groupRow : [select id, name, x1, x2, x3...   from drug_group__c])
            {
                DrugGroupDisp grp = new DrugGroupDisp();
                grp.Setup( groupRow );                                 
                groups.Add( grp);
            }     
        }   
        return groups;
    }

• Max formula size increases from 1000 to 1300 characters.  (No change in the max compiled size limit of 4K)
• No more curly braces on merge fields in formulas:  {!AccountName}  --> AccountName
• Access to “global variables” in formulas: $Organization, $User (current user), $Profile (current user's profile), $UserRole (current user's role)
• Access to Record Type field ($RecordType.Name)
  

• DATEVALUE(datetime), DATEVALUE(text) – Convert a datetime field or a text field to a date field
• FIND (start_text, text [, start_num]) - return the position of the string search_text within the string text
• SUBSTITUTE (text, old_text, new_text) - find instances of the string old_text in the string text and replace with new_text
• BR() – insert a line break in a text formula
• MIN( num1, num2, num3,…) , MAX( num1, num2, num3…) – return the min or max value from the input parameters
• New functions for validation rules: ISCHANGED (field), PRIORVALUE (field), ISNEW()
• Advanced functions for S-Control scripting: LINKTO, URLFOR, INCLUDE, GETRECORDIDS

• HYPERLINK formulas can now use any protocol handler (e.g., "javascript&colon;" instead of "http:")
• IMAGE formulas now work in email and mail merge (Microsoft Word) templates
• TEXT function now accepts datetime values as well as numeric values

• Field Type picklist allows selection of object (current object, $profile, $user, etc.)
• Insert Operator is now a menu button instead of separate buttons for each operator

• Workflow field update actions (Enterprise & Unlimited Edition) - set and store field values in currency, number, percent, text, date, and date/time fields based on a formula expression
• Validation rules - Boolean formula expressions that can prevent incorrect data from being saved
• Default field values - initial values to be populated in fields when new records are created
• Server-side formula expressions for S-Controls