2

It turns out that the answer isn't really a Salesforce thing. By setting the max-age value to -1 (per an example I had encountered), the cookie was immediately expired. By changing it to a valid positive value the expected value was returned. It's unclear to me why an expired cookie shows in Chrome's Application panel, or whether JavaScript would have ...


2

Manipulating things like .xlsx, .docx, and .pdf files is theoretically possible, but practically impossible (no standard functionality for doing zip/unzip on files, poor binary stream support, limited CPU and heap). That's not the type of work that the Salesforce platform is meant to do. This is something that should be handled by another service. Heroku ...


1

You can apply landscape to the entire page using the @page CSS selector. Here is a fully functional version you can use as a starting point: <apex:page renderAs="advanced_pdf" showHeader="false" applyHtmlTag="false" applyBodyTag="false"> <html> <head> <style> ...


1

I don't know a way of doing that with force:showToast, you can obtain a similar result using the lightning:overlayLibrary or creating a custom toast copying the SLDS toast blueprint.


1

You can use the OpportunityContactRoles relationship: <apex:page standardController="Opportunity"> <apex:datatable value="{!Opportunity.OpportunityContactRoles}" var="role"> <apex:column value="{!role.Contact.Name}" /> <apex:column value="{!role.Contact.Email}" /> <...


1

this is answered here https://salesforce.stackexchange.com/a/252338/10073 I cannot find source docs for this, but this is still the case as of January 2021 based on my tests


1

An extension controller must have a constructor that receives an ApexPages.StandardController object (as it's bound to an object standard controller). In your case: public ShowErroronVFPage(ApexPages.StandardController controller){ this.acc = (Account)controller.getRecord(); } Said that: I recommend having a more meaningful name for your standard ...


1

You don't need to query the records, just bind directly to the record in the controller: <apex:page standardController="Opportunity" extensions="Opportunity_UpdExt" docType="html-5.0" sidebar="true" lightningstylesheets="true"> <apex:form> <apex:pageBlock> <apex:...


1

The URLFOR syntax is incorrect. var item represent each record from the candi list, so you can access the record id directly as follows: <apex:outputLink value="{!URLFOR($Action.Candidate__c.view,item.Candidate_Id__c)}" target="_blank"> {!item.Candidate_Id__r.Name} </apex:outputLink> You will need to add field ...


1

Do not use apex:panelGrid/apex:pageBlock/etc if you expect a responsive design. These Visualforce components are not responsive; in fact, there's even a checkbox for Visualforce pages that indicate a page is supported on Mobile, and only those can be used in a mobile app. Developers should only enable the checkbox for pages that use a reactive design, ...


Only top voted, non community-wiki answers of a minimum length are eligible