https://forums.autodesk.com/t5/vault-customization-forum/rest-api-json-classes/m-p/13430879#M72 <P>Part of the response of the <A href="https://aps.autodesk.com/en/docs/vaultdataapi/v2/reference/http/search-GET/" target="_blank" rel="noopener">basic search</A> endpoint has in it's "Included" node a "Folder" node. Easy enough to make the JSON class so far. However, the sub node of "Folder" is the ID of the folder, which changes each time depending on search result. How do you account for the variability in node names in the JSON class?</P> Thu, 17 Apr 2025 12:15:35 GMT jason.johnson3PJE7 2025-04-17T12:15:35Z https://forums.autodesk.com/t5/vault-customization-forum/rest-api-json-classes/m-p/13430879#M72 <P>Part of the response of the <A href="https://aps.autodesk.com/en/docs/vaultdataapi/v2/reference/http/search-GET/" target="_blank" rel="noopener">basic search</A> endpoint has in it's "Included" node a "Folder" node. Easy enough to make the JSON class so far. However, the sub node of "Folder" is the ID of the folder, which changes each time depending on search result. How do you account for the variability in node names in the JSON class?</P> Thu, 17 Apr 2025 12:15:35 GMT https://forums.autodesk.com/t5/vault-customization-forum/rest-api-json-classes/m-p/13430879#M72 jason.johnson3PJE7 2025-04-17T12:15:35Z