Salto for
Salesforce
Articles
SHARE
Pablo Gonzalez
April 12, 2022
4
min read
Today, Salesforce admins and developers don’t have a consistent way to explore their orgs' metadata to find dependencies. Some use VS Code, others use Workbench, and others use various free offerings that only address limited use cases.
That changes today.
We are excited to announce the launch of Salto's Free Tool. It’s a 100% forever free account (not just a trial) that provides Salesforce admins and developers with the following capabilities:
"Where is this used" functionality for all standard and custom fields.
Impact analysis for all metadata types so you can find out where those super sneaky email templates are being used, or what other flows use flows (for example, subflows).
Full metadata search so you can find hardcoded values such as email addresses, profile IDs, and more.
Slack and email notifications for when someone makes changes to your configuration or sensitive metadata.The free tier will provide your team with a single platform so you can stay on top of your Salesforce metadata. And really, why should you have to get approval from your procurement team to find dependencies in your Salesforce org? We believe impact analysis should be free for all.
Salesforce's native "Where is this used" feature lets you see where a custom field is used. However, you are out of luck if you want to know where a standard field (like the Opportunity Stage) is used.
To Salto, a standard field is no different from a custom field. It’s just another configuration element. For example, pictured, Salto can find all references to the Opportunity.StageName field. We can see all the places where the field is used and the exact location of the reference.
When we think about impact analysis in Salesforce, we almost always talk about where a field is used. The truth is, custom fields are just one of many metadata types in Salesforce that other metadata types can use. An example that comes to mind is email templates. It’s difficult to find where they are being used, as they can be used in process builders, flows, workflow email alerts, and Apex. With Salto's full text search, you can simply type in the email template name and find all its references:
The same applies to anything else you can think of. Use it to find hardcoded user IDs, email addresses, and more.
When performing an impact analysis, sometimes you have to compare two pieces of metadata to understand the differences and decide which one to modify. A typical example is comparing one profile against another.Pictured below, our metadata comparison capability makes this a breeze.
Sometimes, impact analysis is not enough. Let's say you really want to know if another developer makes a change to your beautifully crafted account trigger handler. Salto's monitoring service makes it easy to specify which metadata is important to you, and what type of changes you want notifications for.
You can receive the notification via Slack or email. Which is far better than finding out someone changed your code only once it made it to Production.
This is the first version of our free tool. Whether you are an admin, a developer, or an architect, we would love to hear what you like about it and what could be better.
Salto for
Salesforce
Product Updates
SHARE
Pablo Gonzalez
April 12, 2022
4
min read
Today, Salesforce admins and developers don’t have a consistent way to explore their orgs' metadata to find dependencies. Some use VS Code, others use Workbench, and others use various free offerings that only address limited use cases.
That changes today.
We are excited to announce the launch of Salto's Free Tool. It’s a 100% forever free account (not just a trial) that provides Salesforce admins and developers with the following capabilities:
"Where is this used" functionality for all standard and custom fields.
Impact analysis for all metadata types so you can find out where those super sneaky email templates are being used, or what other flows use flows (for example, subflows).
Full metadata search so you can find hardcoded values such as email addresses, profile IDs, and more.
Slack and email notifications for when someone makes changes to your configuration or sensitive metadata.The free tier will provide your team with a single platform so you can stay on top of your Salesforce metadata. And really, why should you have to get approval from your procurement team to find dependencies in your Salesforce org? We believe impact analysis should be free for all.
Salesforce's native "Where is this used" feature lets you see where a custom field is used. However, you are out of luck if you want to know where a standard field (like the Opportunity Stage) is used.
To Salto, a standard field is no different from a custom field. It’s just another configuration element. For example, pictured, Salto can find all references to the Opportunity.StageName field. We can see all the places where the field is used and the exact location of the reference.
When we think about impact analysis in Salesforce, we almost always talk about where a field is used. The truth is, custom fields are just one of many metadata types in Salesforce that other metadata types can use. An example that comes to mind is email templates. It’s difficult to find where they are being used, as they can be used in process builders, flows, workflow email alerts, and Apex. With Salto's full text search, you can simply type in the email template name and find all its references:
The same applies to anything else you can think of. Use it to find hardcoded user IDs, email addresses, and more.
When performing an impact analysis, sometimes you have to compare two pieces of metadata to understand the differences and decide which one to modify. A typical example is comparing one profile against another.Pictured below, our metadata comparison capability makes this a breeze.
Sometimes, impact analysis is not enough. Let's say you really want to know if another developer makes a change to your beautifully crafted account trigger handler. Salto's monitoring service makes it easy to specify which metadata is important to you, and what type of changes you want notifications for.
You can receive the notification via Slack or email. Which is far better than finding out someone changed your code only once it made it to Production.
This is the first version of our free tool. Whether you are an admin, a developer, or an architect, we would love to hear what you like about it and what could be better.