Differences

This shows you the differences between two versions of the page.

--- webapi:examples:inventory_changes [2020/02/20 10:55 (4 years ago)] – kevin
+++ webapi:examples:inventory_changes [2020/02/20 13:57 (4 years ago)] (current) – kevin
@@ Line 11: / Line 11: @@
 </note>
-Sample call requesting the first 1000 inventory filtered by ecommerce and last update data.
+Sample call requesting the first 100 inventory filtered by ecommerce and last update data.
-http://127.0.0.1:8080/Windward/WebAPI/Inventory/InventoryChanges?EffectiveDate=2019-01-01&eCommerceExport=Y&PageSize=1000
+http://127.0.0.1:8080/Windward/WebAPI/Inventory/InventoryChanges?EffectiveDate=2019-01-01&eCommerceExport=Y&PageSize=100
 ===== Sample Inventory Pseudocode =====
@@ Line 43: / Line 43: @@
 ===== TServerMethodsWebAPI\Get_Part_Changes =====
-<note tip>This endpoint is not recommended to use for any large amounts of data as it is known to have speed performance issues and is not efficient.
+<note tip>This endpoint is not recommended to use for any large amounts of data as it is known to have speed performance issues and is not efficient.  If you are using this endpoint for thousands of inventory records, we recommend using the Inventory/InventoryChanges endpoint.
 </note>
-The TServerMethodsWebAPI/Get_Part_Changes returns the list of Part Unique numbers that have changed since the Effective Date.  It translates inside the API using an XML DOM which has a memory and performance impact.  If you are using this endpoint for thousands of inventory, we recommend updating to use Inventory/InventoryChanges.
+The TServerMethodsWebAPI/Get_Part_Changes returns the list of Part Unique numbers that have changed since the Effective Date.  It translates inside the API using an XML DOM which has a known memory and performance impact.
 ===== TServerMethodsWebAPI\Get_Parts =====