Comments
Compressing item ledger entries, or even Value entries would be very helpful. 190 million entries in the value entries is just too much.Would be also interesting to have something for those items that are obsolete in the system. In many cases items are getting obsolete and not used anymore, and after 5-10 years would be interesting to compress or even remove all related data without creating inconsistencies.
Thanks for summarizing, Tyler! I think we mean the same thing, allow me to give another example: Think of the out-of-the-box "Event Registration Created" trigger: today, if you want to use the event or registration data in a downstream Power Automate flow, you have to manually declare and map each field as a custom attribute in the Custom Trigger and then actually set those values when using the trigger within the journey.With this idea, that context would be available in the flow automatically — just as it already is in the email editor. You could directly reference the event registration or event in the flow without having to manually pass them through custom attributes or retrieve them through additional Dataverse lookups in the flow itself.
My understanding of what this IDEA is requesting.Essentially you want to make it easier in custom triggers powered by PA flows on the journey side to access any information from related tables in the PA Flow, correct? Instead of having to code the specific values you want to pass in the PA flow like you have to today.