Field Service Lightning
These help topics guide you through of your
Field Service Lightning (FSL)
using Prodly AppOps Release. Prodly provides pre-built org-to-org deployment toolkits to assist with reference data deployment in your . Each toolkit contains customizable AppOps Release and a as , which provide AppOps Release the deployment instructions it needs for successful org-to-org deployment.
The templates are available in the Prodly User Community
Each data set in the toolkit is a logical grouping of
reference data. You can deploy the data sets one-by-one manually or use the deployment plan to deploy all the data sets with a single click. Because every implementation is unique, data sets are editable so you can make changes to suit your implementation needs.
What's Reference Data?
In any low-code Salesforce app, reference data is data you create during app configuration that is stored as record data within app's objects. Because the reference data is stored as record data and not as code, you cannot deploy the data with change sets or other metadata tools. But deploying the data between Salesforce orgs using a data loader and spreadsheets can be very difficult and time consuming because low-code reference data is highly relational.
Therefore, creating and maintaining an for
using traditional tools is very difficult. Most admins are too time-constrained to follow the best practice of creating and maintaining reference data in a development sandbox, then deploying to a QA sandbox, then to a UAT sandbox for testing and training, and eventually to the production org.
Prodly specifically designed AppOps Release and the deployment toolkits to handle the interrelational nature of low-code app reference data. There are many factors to consider, including the need to deploy data in a specific order to maintain the relationships. The toolkits help you carefully analyze your data to determine the best approach and sequence of deployment events.
AppOps Release does not require the time-consuming process of adding Salesforce external IDs to every object just to maintain the integrity of the relationship IDs in the destination org post-deployment. Instead, AppOps Release provides powerful upsert features which take the standard Salesforce upsert functionality to a whole new level:
Prodly strongly recommends using VEID because, even with concatenated composite IDs, records in some of the
objects are not guaranteed to have unique IDs. The data sets in the toolkit use the VEID upsert functionality and assume your destination org does not initially contain any
If you are starting in the middle of a development cycle and there is existing data in your destination org that was entered by a method other than a sandbox refresh or sandbox cloning (such as a data loader or manual entry), consult with Prodly to determine the best approach to moving forward.
Jump to Top Next topic: Deployment Checklist
© Copyright 2020 Prodly, Inc. All rights reserved. Prodly, AppOps Release, and AppOps Test are trademarks of Prodly, Inc., as are other names and marks. Salesforce and other names are trademarks of salesforce.com, inc., and are used here with permission. Other marks and names appearing herein may be trademarks of their respective owners.