Rollup vs calculated columns in Dataverse: the async trap we fell for
The article discusses the differences between rollup and calculated columns in Dataverse, highlighting a common misunderstanding regarding their functionality. Users often expect rollup columns to provide real-time data, but they actually compute values on a schedule, leading to stale information. The article suggests alternatives for achieving real-time totals when necessary, including plugins and calculated columns on child records.
- ▪Rollup columns compute their values on a schedule, while calculated columns provide real-time data every time a row is read.
- ▪Users often misinterpret rollup columns as real-time aggregates, leading to confusion when data does not update immediately.
- ▪The article outlines three alternatives for obtaining real-time totals, including using plugins and calculated columns on child records.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3948393) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } SapotaCorp Posted on May 24 • Originally published at sapotacorp.vn on May 24 Rollup vs calculated columns in Dataverse: the async trap we fell for #powerplatform A deal desk dashboard showed the running total of opportunities per account. Total amount per account was a rollup column. Users opened the dashboard, saw a total, made a decision. Then someone added a new opportunity and checked the same account. The account's total did not change.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
