Overview
Here are some key concepts to help you grasp the power and fine-grained control Prodly offers. Your understanding of these concepts is essential to successfully deploying only the specific data you desire to deploy.
Relationship Direction
In the Next-Gen Data Set Editor, you select Parent Relationships and Child Relationship objects from the Related tab to create a chain of data set objects that define the direction Prodly traverses your data during deployment. Which objects link to what other objects is totally under your control, and what you choose is vitally important for identifying which records to deploy and in which order.
Understanding relationship direction allows you to avoid including additional extraneous children of a child’s parent. This concept also applies to extraneous parents.
Ignore Relationship Constraint
Conversely to relationship direction, ignore relationship constraint allows you to deploy all records in an object regardless of parent/child relationships. The method is similar to the concept of an outer join. Control this functionality with the Ignore Relationship Constraint toggle found in the non-root object Settings tab.
Enforce Strict Query Filter
Prodly allows you to use query filters to control which records to deploy. Prodly’s intelligence also recognizes and deploys records that are required because of related lookups, even when the records don’t meet your query filter criteria. However, you can instruct Prodly to override its intelligence and deploy only the records that meet your query filter criteria. Control this functionality with the Enforce Strict Query Filter toggle on the Relationship view side panel that is accessed by clicking on the gear icon next to the selected object from the Related tab of the pertaining object, or by clicking on the relationship arrow in the Diagram view.
Copy Relationship Value
When selected, Prodly copies the value of the relationship field from the source record to the destination record. This feature allows you to insert the lookup ID into the destination org record, rather than deploy the parent record data. Control this functionality with the Copy Relationship Value checkbox on the Settings tab in the data set editor Object view.
Copy Relationship Value only works when the parent record exists in the destination org. Errors occur when the parent record does not exist in the destination org. An example of a valid use case is a lookup to User records, because User records are generally present in both the source and destination orgs.
Skip Relationship Processing
In any given data set, each Salesforce object you select for inclusion from the Parent Relationships and Child Relationships list found in the Related tab exists in exactly one data set object, regardless of how many times you pick that object from various lookup relationships. There are use cases though that need to skip processing farther down the data set object chain (that you previously identified on the relationship editor panel) for some of the lookups.
For example, in Salesforce CPQ, product records contain separate relational lookup fields for required product options and optional product options. In this example, to save time and space when copying test data to a sandbox, you can skip deploying the discount schedules, price rules, and more for the optional products by selecting the Skip Relationship Processing toggle for the optional product options on the relationships side panel which is accessed via the gear icon.