There are many different options available in broadcasting newsletter to community users, such as using native Salesforce feature of send email or third party apps from the Appexchange if you have more specific requirements or simply using other applications for marketing purpose.
We have recently implemented this requirement with a combined utilisation of:
- Mail Chimp as the marketing tool
- third party app Chimp Sync from the Appexchange to sync to Salesforce
This implementation has achieved the following requirement:
- subscription list can be made available in Salesforce
- community users can be added to the subscription list for broadcast in Mail Chimp
- community users are able to receive newsletters via email and directly access it
- past and present newsletters will be available in Salesforce
Have you ever encountered the “Maximum view state size limit” error on the Visualforce page that you developed even though you only capture very little information (e.g, like 3 input fields)?
“Maximum view state size limit (135KB) exceeded. Actual view state size for this page was xxx.xxKB”
The way that the view state works is that it is not only holding the value of the field that you capture on the page, but it also holds the value of any accessible objects/variables that you have declared in the controller/extension. For example, if you have an object list (e.g, List<Account>) and the list is holding a lot of records, you might encounter the view state size limit error even though you are not displaying result in the page.
Salesforce has a good explanation on Visualforce View State that gives you a good start if you are troubleshooting the issue. As a good developer, you should also follow the best practice guide to develop a performance optimized Visualforce page.
We are proud to announce that we have released a new version of Boomi JIRA REST connector. This connector helps to reduce the complexity of authenticating and constructing the API request (using JSON format) to JIRA and it works well with any JIRA version 5 and above.
Feel free to check out our the office documentation here for more details.
Recently, I encountered a weird error when trying to delete a batchable Apex class from Salesforce instance. The error was:
This apex class is referenced elsewhere in salesforce.com. Remove the usage and try again.
The reference was pointing to an Apex Job. Initially, this was a bit weird as I had checked that the Apex Job status was shown as Completed before deleting the Apex class. After doing some study, I found that this is related to one of the “error” Apex Job but with status Completed. To be specific, the Apex Job died at the execute() method due to stupid code that I have written and it never reach the finish() method to close the Apex Job execution properly. The Apex Job is still considered open at the backend even though the status is Completed.
If you encounter the similar issue, you can perform the following:
- launch Developer Console
- open Execute Anonymous Windows
- paste the code: System.abortJob(”);
- click Execute to run the script
This should kill off the job and you can proceed to delete the Apex class now.
The client is using SalesLogix to handle credit/loan deals. When the deals are approved, the deal (and the deal related information) need to be in return track in the Sungard Avantgard Integrity system
||To sync approved deals from Saleslogix into Avantgard Integrity system.
||Sage SalesLogix CRM
Sungard Avantgard Integrity
||SalesLogix On-Premise version 8.0.0
Integrity Version 8.4.1
||SalesLogix Deal Roles > Integrity Counter Party
SalesLogix Deal Roles > Integrity BU Exposure Limit
SalesLogix Deal > Integrity Agreement
SalesLogix Deal > Integrity Facility
SalesLogix Deal Tranches and Fees > Integrity Tranche, Fee and Covenant
||JSON and XML
||When a SalesLogix Deal (Custom) is approved, it in return creates an agreement in Integrity. All children information from deal such as contact roles, tranches and fees will create a corresponding Integrity record respectively as well.
||Every 2 minutes
Salesforce Community provides self registration feature so that external user could register for a login if require.
If you are interested to enable this option (From Setup, click Customize | Communities | All Communities, then click Manage next to the community name.), consider if your business require the person account feature so that a self registered personnel will be tracked as a person account in Salesforce.
If person account is not an option for you, you would need to consider implementing a dedicated account being used so that all self registered personnel will be treated as a contact under this specific account instead.
It is also recommended to ensure the profile that you are assigning to for self registered members have the appropriate permission set. Otherwise, the members may be able to view or edit data that you do not want them too.
The users would like to have a mechanism of sending out documents from Salesforce to their clients for signature automatically.
When the quote status is set to “Presented”, a PDF quote containing all the relevant information of the quote including the line items will be generated and sent to the contact for signature automatically.
- Install an app “Conga Composer”.
- Install an app “Conga Workflow”.
- Install an app “Docusign”.
- Create workflow that will be triggered by the quote status.
||Quote, Quote Line Item
||Conga Composer, Conga Workflow, Salesforce Workflow
The client would like to run batch updates on the product price lists quarterly. They have multiple price books and different currencies for each product price
- Product Id: AE110-B
- Product Name: Door Trim (Black)
- Unit price in AUD: 4,200
- Unit price in GBD: 1,500
- Unit price in USD: 4,000
- Product Id: AE110-B
- Product Name: Door Trim (Black)
- Unit price in AUD: 3,900
- Unit price in GBD: 1,000
- Unit price in USD: 3,700
- Install an app “Skyvva”.
- Build a job the updates the pricebook entries.
- Standardise the template used for the update process
||Product, Pricebook, Pricebook Entry
Why are we not able to insert new values to the Campaign Member status field via the Administrator Setup screen just like any other normal picklist field?
This is because the status field picklist value is stored in a standard object called CampaignMemberStatus and it is campaign specific (this means that each Campaign record will have their own specific status picklist value).
How to add new status value?
1. View the Campaign record.
2. Click on the ‘Advanced Setup’ button.
3. Edit the Status or click ‘Add More’ for new status.
Data model relationship:
Insert values using data loader:
Yes, you can use data loader to insert new records into the CampaignMemberStatus object. Note that you will need to include CampaignId field is populated because each status will need to be to related to one Campaign.
How to automate this:
You can try to search for any 3rd party app in AppExchange to automate the process.