Added API for deleted records.

[bartkraai]

No description provided.

[Bertverbeek4PS]

@bartkraai why do you want this API? Also deletion is set to true. There is currently a codeunit that were you is looks up the exporting date and then remove the records.
With an API you can then delete everything which is not recomended

[bartkraai]

This API is used for a customer who wants to track deleted records in their own data-warehouse and delete them if processed. This is maybe a little out of scope for this project but don't see any harm by adding this API.

[Bertverbeek4PS]

This API is used for a customer who wants to track deleted records in their own data-warehouse and delete them if processed. This is maybe a little out of scope for this project but don't see any harm by adding this API.

Why are they not using the codeunit in BC? Because then they are processed if they put it on a weekly base.
By opening the table through an API with deletation on it that is more dangerous that someone remove all the entries with dataloss.

So there is already a good solution for it. And opening it can have allot of implications on it.

[bartkraai]

They use an external warehouse and not fabric to export. So they also process the deleted records themselves. THe delete CU will not work for them.

[Bertverbeek4PS]

They use an external warehouse and not fabric to export. So they also process the deleted records themselves. THe delete CU will not work for them.

Not sure if I understand it.
If you exporting everything with bc2adls it will also export the deleted items.
If there is an export made there will be a timestamp registered.

When you run the codeunit for the deletion it is looking at that timestamp if a record already is exported.