@marije_brummel@LinkedIn Thank you for a well written and important article. One of the things I have been struggling to find a good solution for, is how we in BC can make it visible to the customer, what partner code is well maintained and that way reward the reliable partners
@MansaYay@waldo1001 That is our experience as well in most cases.
Going to the DB once more - and having an ‘optimal’ field list from then on, makes the extra round trip worthwhile.
That being said - the gain from Set/AddLoadFields is less with the new extension model - but still worth your effort
@MansaYay@waldo1001 The performance penalty for missing a field is usually not high, as BC automatically adds ‘missed fields’ to the list when accessed - and invalidates the enumerator - meaning that next page of data retrieved will include the field. But yes, that is slower than getting it right
@diogomiguel_9 But remember - with great power comes great responsibility. We recommend doing ‘surgical’ exclusions - as you can easily remove too much
@KarolakNatalie And unfortunately it is a little simplified. It gets worse when you also consider indirect permissions - so we can make a ‘Permissions calculations - Advanced’ next time 😁
@KarolakNatalie Well - it is called TECHDays, right 😎. That must be the place where this level of geekiness would be appreciated. NB: The slide following this did express the same thing in words.
@mizecaze Thanks, Michael. We hope it will live up to its potential - we are working hard on the UI (and a few other small extras like telemetry if loops are encountered).
Please let us know how it works out for you
@JesperSchulz Looking so much forward to getting on stage with Jesper - and getting your feedback on how we can improve the permission experience even further