9,277
edits
Join the Power Platform Masterclass #2 starting April 23
Storage analyzer: Difference between revisions
Jump to navigation
Jump to search
→Entities report
| Line 66: | Line 66: | ||
Empty columns: resco_description | Empty columns: resco_description | ||
======= Empty | ======= Empty synced entities ======= | ||
campaignitem | campaignitem | ||
| Line 73: | Line 73: | ||
discount | discount | ||
discounttype | discounttype | ||
incident | |||
invoice | |||
… | |||
(By removing these entities from customization you could save … API call(s) in each sync) -> !! | |||
</syntaxhighlight> | </syntaxhighlight> | ||
| Line 86: | Line 91: | ||
* Do you need empty table columns? Their cause a small penalty both in local database operations and in server fetches. | * Do you need empty table columns? Their cause a small penalty both in local database operations and in server fetches. | ||
* Do you need empty | * Do you need empty entities? Each such entity needs 1 fetch during synchronization. | ||
* Label "-> !!" marks tables whose analysis took a long time (right now "too long" means 1+ second). The reason is usually too many rows or too many columns. (Or an older, slower device.) | * Label "-> !!" marks tables whose analysis took a long time (right now "too long" means 1+ second). The reason is usually too many rows or too many columns. (Or an older, slower device.) | ||
* For tables containing too many records: Consider decreasing the row count by designing a stronger [[sync filter]]. | * For tables containing too many records: Consider decreasing the row count by designing a stronger [[sync filter]]. | ||