Establecer como favoritoDeborah Duran (University of Miami) publicó en #NoCodeNovember (Publicado originalmente por Jennifer (Jen) Lee)8 dic 2015, 19:52Jennifer (Jen) Lee@The Blog Group @* Salesforce Administrators * @Solo Admins @No Code November @Women in Tech Have you had a use case where you only want the user to create records s/he created and not all records in the object? Unlike with the edit record function, you can’t use validation rules to prevent record deletion. All roads seemed to lead to solving this via a trigger. Being an Awesome Admin, I wasn’t satisfied with that answer and was determined to find a way to solve for this declaratively. In support of #NoCodeNovember, for the entire month of November, I joined a success community group (@No Code November) dedicated to finding creative ways to deliver features to customers without one line of code. [Read the post on Button Click Admin 5 Reasons to Go #NoCodeNovember to learn more about the group’s genesis.] I was so excited when I solved the following use case using clicks instead of code and wanted to share this with the community in my latest blog article. This works in both Salesforce Classic and Lightning Experience. Hope you are able to find ways to use this for your own use cases as this can be applied to any object, standard or custom. Thanks,JenLimit Record Deletion to Records User Created using Clicks, Not CodeMostrar más1 comentarioJennifer (Jen) Lee (Salesforce)9 dic 2015, 04:49Thanks for sharing!Agregar un comentarioEscribir un comentario...NegritaCursivaSubrayadoTachadoLista con viñetasLista numeradaAgregar vínculoBloque de códigoInsertar imagenAdjuntar archivosURL de vínculoCancelarGuardar0/9000Responder
Jennifer (Jen) Lee@The Blog Group @* Salesforce Administrators * @Solo Admins @No Code November @Women in Tech Have you had a use case where you only want the user to create records s/he created and not all records in the object? Unlike with the edit record function, you can’t use validation rules to prevent record deletion. All roads seemed to lead to solving this via a trigger. Being an Awesome Admin, I wasn’t satisfied with that answer and was determined to find a way to solve for this declaratively. In support of #NoCodeNovember, for the entire month of November, I joined a success community group (@No Code November) dedicated to finding creative ways to deliver features to customers without one line of code. [Read the post on Button Click Admin 5 Reasons to Go #NoCodeNovember to learn more about the group’s genesis.] I was so excited when I solved the following use case using clicks instead of code and wanted to share this with the community in my latest blog article. This works in both Salesforce Classic and Lightning Experience. Hope you are able to find ways to use this for your own use cases as this can be applied to any object, standard or custom. Thanks,JenLimit Record Deletion to Records User Created using Clicks, Not CodeMostrar más