@HemantShukla89@RobSalesforce@karishmalalwani@CherFeldman@bob_buzzard@MuleSoft Sure thing. I think it's important to separate the notion of replicating a copy of the database (what DBAmp does) from what it sounds like you're trying to do, which is build a comprehensive audit history of every single CRUD operation (even beyond just field changes).
@HemantShukla89@RobSalesforce@karishmalalwani@CherFeldman@bob_buzzard@MuleSoft If it's that important to them, they'll find budget for it. Worst case you're right, triggers everywhere to capture every change, write to a central audit table, and push that audit table out to the other database (clearing it out in SFDC every so often). Yuck all the way down.
@HemantShukla89@RobSalesforce@karishmalalwani@CherFeldman@bob_buzzard@MuleSoft As Jay said, CDC isn't going to be 100% reliable for this, so the client should understand that. If they require perfect accuracy with this, you're probably looking at Shield / upgraded field history tracking, then batch pull all the various History tables.
@HemantShukla89@CherFeldman@bob_buzzard@MuleSoft An audit of every single CRUD operation is fairly intense, DBAmp isn't really designed to do that from what I've seen, it's more geared toward getting an operational set of the data into SQL. The grab every CRUD you'd have to drive events out of SFDC.
@CherFeldman@HemantShukla89@bob_buzzard@MuleSoft Agree with Cheryl, what does work with CDC, what specific issues are you up against?
I've used DBAmp in the past to replicate to SQL, it works very well, and is reasonably priced: https://t.co/z53jHmmsk2
@britishboyindc@StephanieFoerst It is a variation of that which won't be recognized as a KI (I asked), because it's a net-new work item, so not a bug. Work Item is W-7939338.
@StephanieFoerst@britishboyindc True, seek alternatives! But to Peter's point on another thread he wrote, there are some use cases (e.g. editing a record), there's no workaround other than without sharing, and that's broken if launched from Visualforce it seems.
@britishboyindc I found a bug that impacts Visualforce running on Sites (basically VF has internal checks that prevent Without Sharing from doing its job) that is just entering the development cycle. Hopefully it's fixed before Winter '21 gets here?
Quick reminder that Summer 20 is going live now, and if you didn't disable the Guest Site Security update, it will now be enabled by default.
But good news is that if your site stops working, you can still disable it again in sharing settings (at least until Winter 21 rolls out)