• Sunil Damle 7
  • NEWBIE
  • 0 Points
  • Member since 2015

  • Chatter
    Feed
  • 0
    Best Answers
  • 0
    Likes Received
  • 0
    Likes Given
  • 3
    Questions
  • 1
    Replies
We have overriden the Standard 'view' action on the Opportunity Object.

We have two different Record types - Type A and Type B. 

Type A - navigates to Custom visualforce page
Type B - Navigates to Standard page.

To achieve this we have used "Nooverride" parameter. See code below.

Post Winter 17 release in the sandbox, the application doesnt respect the "nooverride' paramter and the view action is going into infinite loop in Salesforce lightning app. 

Let me know if you have faced similar issue and any workaround that worked for you.

------------------------------------------------------------------
if (c.recordtypeid == recordTypeId[0].id) {
               
            newPage = Page.CustomVFPage;
        } else {
            newPage = new PageReference('/' + c.id +  '?nooverride=1');
            newPage.getParameters().put('nooverride', '1');
        }
 
We have overwritten the "View" action on the object and are using sforce.one.navigateToURL('/recordId?nooverride=1')  method with "nooverwrite" set to '1' for certain record type to go to standard page. This works will till winter 17 release came to the sandbox.

After the winter 17 release, our view action is going into Continuous loop and standard view page is not loading. Navigate to custom page for record type 'A' works fine.

Amny idea?
Hi,
 I have a requirement to send an email to a team of co-ordinators for which I used the process builder. The process builder checks the type of event and then process would go to a appropriate action branch and an email alert will be sent. As you know, email alerts are associated with Recepients so all I need to do is check the type of event and perform an action of sending an email alert.
We have different set Co-ordinators for each event type.

But as design best practice, this what I want to do -
1. If we add a new event type 'XYZ'(this would be data setup) then I would create a email alert with same name 'XYZ' (again, just data setup, no configuration change)
2. My logic would then see the event type is XYZ so query for the email alert with the same name and would send the email


This way, if any new event type is added in future, I dont need to chagne the process or any logic.

But my problem is that, I dont seems to have a way to query for eMail alert. Has anyone impemented this? Or any other way you can suggest(even using Apex) which will meet the purpose of not changing the code/logic/process for adding a new event type and new email alert.
 
We have overwritten the "View" action on the object and are using sforce.one.navigateToURL('/recordId?nooverride=1')  method with "nooverwrite" set to '1' for certain record type to go to standard page. This works will till winter 17 release came to the sandbox.

After the winter 17 release, our view action is going into Continuous loop and standard view page is not loading. Navigate to custom page for record type 'A' works fine.

Amny idea?