6

There's no real solution outside of "saving frequently," at least within salesforce.com itself. You could turn on the "timeout popup" box, so they can at least know they need to log back in before continuing. Also, you can increase the session time to the maximum, which should last for an entire work day worth of time. If your users are using Chrome or ...


5

I wouldn't necessarily call it the perfect solution, but here are some ideas I've used to make my code more maintainable. Separate your Visualforce action method from your save method that performs DML operations. You never want your user to see the white exception screen so you want to catch all exceptions in your action method. But these exceptions ...


4

You need to use value parameter of the apex:selectList: A merge field that references the controller class variable that is associated with this selectList. For example, if the name of the associated variable in the controller class is myListSelections, use value="{!myListSelections}" to reference the variable. If multiselect is true, the value ...


4

The only supported way to achieve this is through Visualforce, by overriding the entire page. You can't customise the flow of the standard pages, outside of hacking some JavaScript in the sidebar, but even if you go that route it is highly likely to stop working in Summer 15. One way I've used to achieve similar functionality to that you require is to add a ...


3

var recId = result.recordId; result is not defined? you must declare your result variable: var result = something. So, I am guessing you should get the response as follows: var result = saveResult.getResponse().SOMETHING; After updating your post, the server response is actually in your saveResult variable, in order to fetch the recordId from it, just ...


2

Take a look at the URL for the recordtype selection page for the object in question. For Opportunity for example, it's: /setup/ui/recordtypeselect.jsp?ent=Opportunity&retURL=<VF_page>&save_new_url=006/e 006/e being the standard Opportunity edit page. It should be a similar approach for all objects.


2

It sounds like it could be a caching issue. Check out Caching Force.com Sites Pages. The behavior is dependent on the configuration of your site (e.g., login-enabled) and apex:page cache and expires attributes.


2

Those types of url hacking are not supported by Salesforce, but are possible by raising a case. There are however security risks as a consequence of implementing them: How can I allow "autosave by URL"?


2

If you assign the force:recordData recordId attribute, you can use code like the following in your callback: var recId = component.get("v.recordId"); Likewise, the following should also work: var recId = component.find("inventionRecordCreator").get("v.recordId");


1

Why this code failed in creating a new record? If you look at the error it is saying "Attempt to De-reference a null object". And the error was at line Event.EventDates__c = datesFromCalendar; What is happening? Instance Event of the Event__c object trying to set the value of a field EventDates__c. And this object isn't exists actually at first. Before ...


1

I was able to create a workaround using a Lightning Component Action and I have written about my solution and provided links to my repo with the example code here: Link to my post on the solution for quote button in SF1 I hope this is useful for someone else who might get stuck with the same issue. We have a heavy mobile user base so this was very ...


1

If you are trying to insert a new record (as opposed to simply updating an existing one), then the cardRequest.ID != NULL condition will never be satisfied because the record Id is null until after it is inserted, so stdController.save() won't run. Your error messages aren't showing up on the page because the message is lost when the page is refreshed. ...


1

If you add a save method to your controller it will be used instead of the standard save method provided by the standard controller. So whatever you want to happen when the user clicks save you will have to write. After rereading I get what you are asking now: You can add another method to use the current save() method then after that is finished ...


1

You can replace the standard "New" and "Edit" pages by writing a Visualforce page and controller that uses the controller extension pattern. Then within the save method of the controller extension you can make the webservice callout and if it is successful call the standard controller's save method or otherwise output an error message. However, this does ...


1

As @BobBuzzard said it's only possible using a workaround (please don't call it hack). But if you really go on, don't do it this way: http://bobbuzzard.blogspot.co.uk/2014/06/javascript-in-salesforce-home-page.html This will even stop to be usable in a few days (on summer'14 upgrade!), because you won't be able to save the Text-Areas containing script-tags. ...


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