Comments
Ooo, if that "record state" was a Platform enum, right?Imagine if tables could be configured with a new Property called "SoftDelete" that lets users delete data, but it only is soft deleted for 30 days?Still run the OnDelete trigger, and if someone restores the record, it's still treated in (AL) as an OnInsert, but the record comes back from SoftDelete with the same PK and ID (or errors if a new record with the same PK already exists).I'm thinking of people who... oh, delete Salesperson/Purchasers that are used in approval flows, for example.
One way of controlling your cash flow and also helping small customers get their payments done, is to use SEPA Direct Debit collections. So in my company we offer a payment discount to encourage customers to use this option and sign the mandate agreement.When creating the DD collection, the system completely ignores the payment terms set of the SEPA DD. I can see the payment discount on the customer ledger entry, but when reading the code, it only considers "Remaining amount", again completely ignoring "payment discount possible" within the payment discount date and payment tolerance date if that is set up.To me this is not new functionality, this is a bug in finding the right amount to withdraw from customer bank account. I am finding it very difficult to explain why it should work like that, when it works differently in all other instances. As long as the direct debit is made within the payment discount date, the amount should be reduced accordingly, Pls fix!
Per my MS Support ticket: Microsoft have the existing GetAuditStorageDetails API. https://url.au.m.mimecastprotect.com/s/HPbcCQnMQAsX8ENOIxfAcGQV8W?domain=learn.microsoft.comThis provides granular information that would be extremely helpful to see within the Power Platform Admin Centre.This will help to address which tables are generating substantial audit records, in order to then have the information to act accordingly. Using this concept, I'd like to see a similar GetActivityStorageDetails API. So that we can see more granularly, which tables are contributing most substantially to Activity storage consumption.