All Ideas

Idea Details

Upvote Downvote

Post an Idea

640 Points

Open

Andrew Gill

Partial Sandboxes needs to keep Hierarchical integrity of data

Operational Reporting

The new Partial Sandbox did not hit the mark for related hierarchial data that must be considered a single entity. The current partial extract is using a random selection of rows, so although it ensures children have a parent it does not provide the ability to ensure a parent has all it's children.

We have relational/hierarchial set of data that represents a clinical trial. The clinical trial project is a top level object with at least four levels of related data, this could be data collected over months and years. Some parent objects are slected with no children and as you go down the hierarchy you randomly have some children with data and some with none and never a complete set of children. Without all the related children you cannot adequately test or use this data. You may have gaps in time periods, etc.

Please provide the ability to specify a particular record in an object and then chase all related data for that record so that we have a complete unit. The 10,000 row limit is also going to be a problem because as you get down the hierarchy the number of related records will increase especially where you have very granular data like time reported against a trial. If we had a 10,000 limit we would in the end only be able to have a couple of clinical trials being part of the new sandbox.

Merge Idea · Flag

Comments ( 17 )

Sort By

Stuart Fleming - 2 years ago

Its a wonder that any one would use salesforce given this issue.
- Flag

Glen Powell - 2 years ago

I have no hope of ever seeing this implemented, but I'll upvote it as it's totally sensible and an obvious flaw in the existing arrangement.

A relational database which does not preserve referential integrity of copied records in it's dev environment is pretty ridiculous.

With Full Sandboxes being costed at 30% of total subscription price (!), little incentive for SF to bother fixing the "included" environments.

Flag

Marleene Nolan - 3 years ago

Sorry to say I wasted a lot of time in my 'partial sandbox' because I did not realize that referential integrity is not enforced in my sandbox. Note to self, check all data before testing in sandbox!

Should be a given that no matter what the selection process is for creating a partial sandbox, that referential integrity be enforced.

Also see Idea https://success.salesforce.com/ideaView?id=08730000000DkosAAC, 'Enhancements to Partial Sandbox Creation'

Flag

Gnanasekaran Thoppae - 3 years ago

For better data integrity and use in tests, it is important to provide a way to slice the data in its compleness. This is very important for us as we do several parallel projects and re-uploading missing data is very time consuming and repetitive thus not supporting productivity.

Flag

Bob Bailey - 3 years ago

This is a continuing problem for me. While I offer a big THANKS for the Partial Copy Sandbox I would be happier if I could have more control over what goes into the sandbox. For example,all contacts with a last name that begins with C (C*).
Thanks... Bob

Flag

Scott Mercer - 4 years ago

The referential integrity issue bit me big time this weekend. I tried to use a client's partial sandbox to stage a production deployment and ended up abandoning the partial as a staging environment due to these issues.

Maintaining referential integrity is essential in producing sandboxes you can trust. Adding the ability to filter data on each object based on custom criteria would be an acceptable workaround.

Flag

Manjith Radhakrishnan - 4 years ago

I second others. This is a MUST HAVE feature.
- Flag

Roy Lloyd - 4 years ago

This is an absolute MUST HAVE especially since Salesforce Support are recommending this as a solution to an error picked up by a validation rule in a partial copy sandbox.

My Case ID = 5000M00000gScoLQAS
The Error =

"Invalid (ORA-20001:
ORA-06512: at "HAPPY.SACCESS", line 502
ORA-01403: no data found
ORA-06512: at "HAPPY.CACCESS", line 2846
ORA-06512: at "HAPPY.CACCESS", line 2771
ORA-06512: at line 1

SQLException while executing plsql statement: {call cAccess.check_entity_access_proc_ncu(?,?,?,?,?,?)}(EXCLUDED, EXCLUDED, 0013000000cZEmh, EXCLUDED, true, false))"

Flag

Mary C - 4 years ago

Partial sandbox is a great and less expensive option than a full sandbox. Definitely need to keep referential integrity. Another nice feature would be high level filters, e.g. Accounts where Country = United States.

Flag

Eljon Greene - 4 years ago

Facing this issue right now. It's definitely an impediment for data integration projects.
- Flag

Akbar R - 4 years ago

Do this or give ISVs the power to hand out full sandboxes for free so our customers can test updates to the platform and our AppExchange packages on a regular basis without the lack of sufficient data.

Flag

Tony Cirelli - 4 years ago

Agreed ... randomness and referential integrity do not go together.
- Flag
Chase Bass - 4 years ago

This needs to be fixed. It can cause many issues. There are decoupling problems as well.
- Flag

Mike Merino - 4 years ago

further problem. Off of an account record in production I have a custom product (which has a lookup to account). The random creation made a product but not the account. So I manually created the account and they still didn't link. reason:
the product lookup uses the production id of account( 001C000000ul1bBIAQ ),
whereas the manually created account had a different ID ( 001W000000LOMs9 ) when I manually changed the product lookup to the 001W id it linked but this is a huge hassle.

Better solution is this idea, keep Hierarchical integrity of data

Flag

Julie Akawie - 5 years ago

Mind blown. How can you have a relational database that doesn't honor referential integrity?
- Flag

Andrew Gill

7 years ago

640 Points Open

Ideas

Apps

from AppExchange

Questions

No results found.

COVID-19

All Ideas

Idea Details

Comments ( 17 )

Ideas

Apps

Questions

Links

Salesforce

Need Help?