Pavel Kabir Posted March 2 Share Posted March 2 (edited) The legacy readByQuery in the XML API supported specifying "*" in the field list, which was perfect for: Local troubleshooting in Postman, without having to look up the object model first to see what fields are available and tedious copy-pasting User-initiated query's where the user "wants everything" in a tabular form without having to specify an explicit "SELECT". Unfortunately, query in XML / REST based API does not support this. Right now, to enable this scenario, we need to warm up local object definition caches and inspect the model the user wants, so as to retrieve the available field list. It would be so great (save an extra API call and improve report responsiveness), if we could pass a "*" to the query just as we could to legacy readByQuery in the XML API. We discussed this idea briefly with Louis at Transform and he thought it was an great suggestion, so I am filing it here. Edited March 2 by Pavel Kabir Clarification Link to comment Share on other sites More sharing options...
Sterio, Louis Posted March 5 Share Posted March 5 I met with engineering and the architect on this, they are purposely excluding this due to performance reasons. 2 Link to comment Share on other sites More sharing options...
Pavel Kabir Posted March 6 Author Share Posted March 6 That's a pity... We nevertheless provide our users with such a capability, however this happens at the expense of an extra API call to obtain the object definition. For now it feels like it's a common debugging and "drafting" scenario (retrieve everything, see what's inside, then narrow down the data to the columns that you need), but with the workaround above it may actually have worse performance than if "*" was allowed in the first place... 1 Link to comment Share on other sites More sharing options...
Recommended Posts