75
from https://github.com/microsoft/AL/issues/6316
Partial records 'just' landed, and with that we can pass a list of field IDs to `RecordRef.SetLoadFields()` in order to dynamically load fields while also ensuring we don't pull out columns we don't care about.
Now would be a great time to add the long-missing equivalent for FlowFields, i.e. `RecordRef.SetAutoCalcFields()`. This would let us avoid having to do two SQL calls, one for the initial `Get()`/`FindFirst()` and one to actually bring over the FlowField, which is wasteful (especially if, presumably, it needsa separate CalcField() call for each field!!)
This seems to be an omission and would be good to bring up to parity between normal and flow fields. Thanks!
Partial records 'just' landed, and with that we can pass a list of field IDs to `RecordRef.SetLoadFields()` in order to dynamically load fields while also ensuring we don't pull out columns we don't care about.
Now would be a great time to add the long-missing equivalent for FlowFields, i.e. `RecordRef.SetAutoCalcFields()`. This would let us avoid having to do two SQL calls, one for the initial `Get()`/`FindFirst()` and one to actually bring over the FlowField, which is wasteful (especially if, presumably, it needsa separate CalcField() call for each field!!)
This seems to be an omission and would be good to bring up to parity between normal and flow fields. Thanks!
STATUS DETAILS
Needs Votes
Business Central Team (administrator)
Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future. Best regards, Business Central Team