when you reestablish a quantity schedule or you delete an opportunitylineitem the record is not soft deleted by having it's isdeleted flag set to true it is instantly hard deleted.

If you use the workbench or the dataloader (export all set) the records are not returned.

Is this standard SFDC behaviour / can soft deleting opportunityline items as well as schedules be enabled?

It makes data replication very difficult if you can't query for deleted opportunitylineitem / schedule records

Currently we have are creating opportunity line item records as part of an integration from our quoting system.
We then have logic within the after trigger on opportunity line item that is updating the opportunity line item quantity amongst a lot of other things, however it is capable of setting the quantity to 0.

There is a SFDC system design limitation / validation that doesn't allow you to do this, however we somehow are able to. We can reproduce this issue and due to the number of transactions the ETL user does in production it isn't possible to get debug logs from it due to the limit of 20.....

Anyone's assistance in helping to get the bottom of this would be greatly appreciated. Just understanding how it is possible to bypass this system validation.

Note if we then edit that line item with a quantity of 0 within the SFDC UI we are immediately presented with the SFDC platform validation that quantity cant be 0

We have also confrimed that via the UI, apex anonymouns and a very simple trigger it isn't possible to set the quanity to 0

Currently we have are creating opportunity line item records as part of an integration from our quoting system.
We then have logic within the after trigger on opportunity line item that is updating the opportunity line item quantity amongst a lot of other things, however it is capable of setting the quantity to 0.

There is a SFDC system design limitation / validation that doesn't allow you to do this, however we somehow are able to. We can reproduce this issue and due to the number of transactions the ETL user does in production it isn't possible to get debug logs from it due to the limit of 20.....

Anyone's assistance in helping to get the bottom of this would be greatly appreciated. Just understanding how it is possible to bypass this system validation.

Note if we then edit that line item with a quantity of 0 within the SFDC UI we are immediately presented with the SFDC platform validation that quantity cant be 0

We have also confrimed that via the UI, apex anonymouns and a very simple trigger it isn't possible to set the quanity to 0