Skip to content

Commit 5b1fca2

Browse files
authored
Removes redundant configuration entry
1 parent fd8a11f commit 5b1fca2

File tree

1 file changed

+0
-1
lines changed

1 file changed

+0
-1
lines changed

content/reference/configuration.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,6 @@ This includes options to change how many metadata items are included in a single
3838
| `ORGFLOW__METADATAPI__MINRETRIEVEBATCHSIZE` | `--c:metadataapi:minretrievebatchsize` | The minimum number of metadata items that OrgFlow should aim to include in each retrieve batch. | `200` |
3939
| `ORGFLOW__METADATAPI__MAXRETRIEVEBATCHSIZE` | `--c:metadataapi:maxretrievebatchsize` | The maximum number of metadata items that OrgFlow should aim to include in each retrieve batch. | `1000` |
4040
| `ORGFLOW__METADATAPI__MINNUMBERRETRIEVEBATCHES` | `--c:metadataapi:minnumberretrievebatches` | The minimum number of retrieve batches that OrgFlow should aim to create. This value does not impact the minimum number of metadata items that OrgFlow should aim to include in each retrieve batch, but it can impact the maximum number of metadata items that OrgFlow should aim to include in each retrieve batch. For example, if there aren't enough metadata items to fill each batch, OrgFlow will lower the maximum number of metadata items in each batch in order to try and hit the minimum number of retrieve batches target. However, if there aren't enough metadata items to hit the minimum number of retrieve batches target, then OrgFlow will favor reducing the number of batches that it creates as opposed to lowering the minimum number of metadata items that OrgFlow should aim to include in each retrieve batch. | `16` |
41-
| `ORGFLOW_METADATAPI__MAXDEPENDENTSBATCHUTILIZATIONPERCENT` | `--c:metadataapi:maxdependentsbatchutilizationpercent` | Metadata items such as Profiles (which depend on CustomObjects, CustomTabs, and ApexClasses among others) and Translations (which depend on CustomLabels, CustomTabs, and QuickActions among others) can be included in more than one batch because they need to be retrieved in that same batches as their dependencies. This value aims to reduce the duplication of these items between batches by increasing the maximum number of metadata items that OrgFlow should aim to include in each retrieve batch if the number of dependent items is too large compared to their dependencies. For example: if the target retrieve batch size is 1,000 items, a batch contains 600 Profiles, and this value is set to 50%, then OrgFlow will add more items to the retrieve batch to in order to ensure that the retrieve batch is made up of no more than 50% Profiles (i.e. OrgFlow will aim to put 1,200 items in this batch). | `50` |
4241

4342
### Metadata Archives
4443

0 commit comments

Comments
 (0)