Updated readme with image and more detailed descriptions
Browse files
README.md
CHANGED
|
@@ -1,10 +1,14 @@
|
|
| 1 |
---
|
| 2 |
license: apache-2.0
|
| 3 |
---
|
| 4 |
-
|
| 5 |
-
|
| 6 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
| 7 |
|
| 8 |
Note that most queries (all single API queries and many double API queries) contain local IDs which will not work directly on a new dataset. The IDs must point to real objects for the API calls to execute.
|
| 9 |
|
| 10 |
-
However, it is not essential for an API call to fully execute to judge its correctness, unless it is the first step of a two-part query.
|
|
|
|
| 1 |
---
|
| 2 |
license: apache-2.0
|
| 3 |
---
|
| 4 |
+
|
| 5 |
+

|
| 6 |
+
|
| 7 |
+
|
| 8 |
+
This dataset consists of 2 files, containing 200 total queries:
|
| 9 |
+
1) 142 single-API queries in "singleAPI_142_queries.csv"
|
| 10 |
+
2) 58 double-API queries in "multiAPI_58_queries.csv"
|
| 11 |
|
| 12 |
Note that most queries (all single API queries and many double API queries) contain local IDs which will not work directly on a new dataset. The IDs must point to real objects for the API calls to execute.
|
| 13 |
|
| 14 |
+
However, it is not essential for an API call to fully execute to judge its correctness, unless it is the first step of a two-part query. In the latter case, we recommend replacing the IDs with real IDs from a user's specially created hubspot dataset.
|