How to pre-populate fields when creating a new record? [duplicate]





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty{ margin-bottom:0;
}






up vote
0
down vote

favorite













This question already has an answer here:




  • Custom URL Hack - anybody know how can i find the fields IDs from “User” object?

    2 answers




I have a custom parent object A and a child object B.



When I create a new record from the child object B via the related list, only the parent lookup field is defaulted and filled in.



When I hit create new in the related list, I need to add more fields to be auto filled in.



Is there an appropriate solution to such issue?



Please advise if there is a way by using the process builder or some other means of automation processes?










share|improve this question













marked as duplicate by David Reed, battery.cord, glls, Raul, Mohith Shrivastava Nov 28 at 3:08


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.















  • Lightning or Classic?
    – David Reed
    Nov 27 at 16:32










  • Classic version
    – lemdev
    Nov 27 at 16:34










  • if the fields are not mandatory, you can use a workflow rule, a Process builder and so on. After, the user should edit.
    – m Peixoto
    Nov 27 at 16:39

















up vote
0
down vote

favorite













This question already has an answer here:




  • Custom URL Hack - anybody know how can i find the fields IDs from “User” object?

    2 answers




I have a custom parent object A and a child object B.



When I create a new record from the child object B via the related list, only the parent lookup field is defaulted and filled in.



When I hit create new in the related list, I need to add more fields to be auto filled in.



Is there an appropriate solution to such issue?



Please advise if there is a way by using the process builder or some other means of automation processes?










share|improve this question













marked as duplicate by David Reed, battery.cord, glls, Raul, Mohith Shrivastava Nov 28 at 3:08


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.















  • Lightning or Classic?
    – David Reed
    Nov 27 at 16:32










  • Classic version
    – lemdev
    Nov 27 at 16:34










  • if the fields are not mandatory, you can use a workflow rule, a Process builder and so on. After, the user should edit.
    – m Peixoto
    Nov 27 at 16:39













up vote
0
down vote

favorite









up vote
0
down vote

favorite












This question already has an answer here:




  • Custom URL Hack - anybody know how can i find the fields IDs from “User” object?

    2 answers




I have a custom parent object A and a child object B.



When I create a new record from the child object B via the related list, only the parent lookup field is defaulted and filled in.



When I hit create new in the related list, I need to add more fields to be auto filled in.



Is there an appropriate solution to such issue?



Please advise if there is a way by using the process builder or some other means of automation processes?










share|improve this question














This question already has an answer here:




  • Custom URL Hack - anybody know how can i find the fields IDs from “User” object?

    2 answers




I have a custom parent object A and a child object B.



When I create a new record from the child object B via the related list, only the parent lookup field is defaulted and filled in.



When I hit create new in the related list, I need to add more fields to be auto filled in.



Is there an appropriate solution to such issue?



Please advise if there is a way by using the process builder or some other means of automation processes?





This question already has an answer here:




  • Custom URL Hack - anybody know how can i find the fields IDs from “User” object?

    2 answers








custom-object process-builder automation process-automation






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 27 at 16:31









lemdev

586




586




marked as duplicate by David Reed, battery.cord, glls, Raul, Mohith Shrivastava Nov 28 at 3:08


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.






marked as duplicate by David Reed, battery.cord, glls, Raul, Mohith Shrivastava Nov 28 at 3:08


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.














  • Lightning or Classic?
    – David Reed
    Nov 27 at 16:32










  • Classic version
    – lemdev
    Nov 27 at 16:34










  • if the fields are not mandatory, you can use a workflow rule, a Process builder and so on. After, the user should edit.
    – m Peixoto
    Nov 27 at 16:39


















  • Lightning or Classic?
    – David Reed
    Nov 27 at 16:32










  • Classic version
    – lemdev
    Nov 27 at 16:34










  • if the fields are not mandatory, you can use a workflow rule, a Process builder and so on. After, the user should edit.
    – m Peixoto
    Nov 27 at 16:39
















Lightning or Classic?
– David Reed
Nov 27 at 16:32




Lightning or Classic?
– David Reed
Nov 27 at 16:32












Classic version
– lemdev
Nov 27 at 16:34




Classic version
– lemdev
Nov 27 at 16:34












if the fields are not mandatory, you can use a workflow rule, a Process builder and so on. After, the user should edit.
– m Peixoto
Nov 27 at 16:39




if the fields are not mandatory, you can use a workflow rule, a Process builder and so on. After, the user should edit.
– m Peixoto
Nov 27 at 16:39










1 Answer
1






active

oldest

votes

















up vote
5
down vote



accepted










In lightning: you can do that using Set Predefined Field Values for Quick Action Fields. Here you predefine values for the new record created in quick action attributes and thus they gets prepopulated when you click the quick action button.



In Classic : In classic you can use URL hacking : Here you pass the FieldID and its value in URL params and they get set in the corresponding fields accordingly.



Src : https://help.salesforce.com/articleView?id=predefined_field_values.htm&type=5



Src : https://www.salesforceben.com/salesforce-url-hacking-tutorial/






share|improve this answer




























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    5
    down vote



    accepted










    In lightning: you can do that using Set Predefined Field Values for Quick Action Fields. Here you predefine values for the new record created in quick action attributes and thus they gets prepopulated when you click the quick action button.



    In Classic : In classic you can use URL hacking : Here you pass the FieldID and its value in URL params and they get set in the corresponding fields accordingly.



    Src : https://help.salesforce.com/articleView?id=predefined_field_values.htm&type=5



    Src : https://www.salesforceben.com/salesforce-url-hacking-tutorial/






    share|improve this answer

























      up vote
      5
      down vote



      accepted










      In lightning: you can do that using Set Predefined Field Values for Quick Action Fields. Here you predefine values for the new record created in quick action attributes and thus they gets prepopulated when you click the quick action button.



      In Classic : In classic you can use URL hacking : Here you pass the FieldID and its value in URL params and they get set in the corresponding fields accordingly.



      Src : https://help.salesforce.com/articleView?id=predefined_field_values.htm&type=5



      Src : https://www.salesforceben.com/salesforce-url-hacking-tutorial/






      share|improve this answer























        up vote
        5
        down vote



        accepted







        up vote
        5
        down vote



        accepted






        In lightning: you can do that using Set Predefined Field Values for Quick Action Fields. Here you predefine values for the new record created in quick action attributes and thus they gets prepopulated when you click the quick action button.



        In Classic : In classic you can use URL hacking : Here you pass the FieldID and its value in URL params and they get set in the corresponding fields accordingly.



        Src : https://help.salesforce.com/articleView?id=predefined_field_values.htm&type=5



        Src : https://www.salesforceben.com/salesforce-url-hacking-tutorial/






        share|improve this answer












        In lightning: you can do that using Set Predefined Field Values for Quick Action Fields. Here you predefine values for the new record created in quick action attributes and thus they gets prepopulated when you click the quick action button.



        In Classic : In classic you can use URL hacking : Here you pass the FieldID and its value in URL params and they get set in the corresponding fields accordingly.



        Src : https://help.salesforce.com/articleView?id=predefined_field_values.htm&type=5



        Src : https://www.salesforceben.com/salesforce-url-hacking-tutorial/







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 27 at 16:38









        Pranay Jaiswal

        11.7k31951




        11.7k31951















            Popular posts from this blog

            AnyDesk - Fatal Program Failure

            How to calibrate 16:9 built-in touch-screen to a 4:3 resolution?

            QoS: MAC-Priority for clients behind a repeater