Podcast #128: We chat with Kent C Dodds about why he loves React and discuss what life was like in the dark days before Git. Listen now.
2

You can transfer the results back to the client, then initiate a download. // client code let action = component.get("c.orderRecord"); action.setParams({ OrderRecId: recordId }); action.setCallback(this, result => { if(result.getState() === 'SUCCESS') { let downloadLink = document.createElement('a'); downloadLink.download = 'example.pdf'; ...


1

It was the periods in the inputCheckbox id's. After removal and replace with - it worked like a dream


1

I found the issue after rebuilding the VF page little by little. It turns out that I had two tags for the form class="form-horizontal". Perhaps adding ids would have solved the problem but removing one of them the trick and everything is working. I appreciate all the help!! <apex:form> <form class="form-horizontal" role="form" action="#"> <...


1

You're basically trying to store every record in the database in the view state. This is not going to work. Even if you didn't get a view state size error, you'd get errors for querying too many records, etc. You'll want to read about dynamic queries. This will greatly improve your code's performance and allow you to avoid view state size errors, heap limit ...


1

That is not the way to generate the visualforce dynamically, the other simpler way I can think of is to write two output links and render it based on your conditions. Your visualforce page which would work would be <apex:outputPanel rendered="{!showSign}"> <apex:outputPanel rendered="{!IF(signStatus == 'Unsigned', true, false)}"> ...


1

The "Lightning StyleSheets" attribute only adds the look of Lightning, but does not actually contain the full runtime. You need to expose the flow in a Lightning App or Lightning Component. Use lightning:flow to expose a flow in a compatible experience.


1

The framework automatically destroys the old instance once unset from the attribute. There is no need to take additional action. cmp.set("v.fAttr", [newButton]); The documentation states you only need to manually destroy components if you never assign them to an attribute of the type Aura.Component[]. After a component that is declared in markup is no ...


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