'null' entities fetched when using --readEntities
Closed this issue · 2 comments
~/Git/web-api-commander/out $ java -Dlog4j.configuration=file:/home/dylan/Git/web-api-commander/out/log4j.xml -jar web-api-commander.jar --readEntities --inputFile metadata_file --outputFile outputfile2 --limit -1 --uri "https://sparkapi.com/Reso/OData/Property?\$count=true&\$select=ListingKey,ListingId,PoolFeatures,PropertyType" --bearerToken [redacted] [INFO] [11:44:28.235] Reading all entities from: https://sparkapi.com/Reso/OData/Property?$count=true&$select=ListingKey,ListingId,PoolFeatures,PropertyType [INFO] [11:44:41.959] null entities fetched: [INFO] [11:44:41.962] ClientEntityImpl [id=https://sparkapi.com/Reso/OData/Property('20000612234841842201000000'), eTag=null, mediaEntity=false, mediaContentType=null, mediaContentSource=null, mediaETag=null, editLink=null, properties=[ClientPropertyImpl{name=ListingId, value=00-7, annotations=[]}, ClientPropertyImpl{name=ListingKey, value=20000612234841842201000000, annotations=[]}, ClientPropertyImpl{name=PropertyType, value=Residential, annotations=[]}], annotations=[], typeName=null, navigationLinks=[], associationLinks=[], mediaEditLinks=[], operations=[]super[AbstractClientPayload [contextURL=nullsuper[ClientItem [name=null, link=null]]]]]
Should return the count instead.
@dgmyrek I think this issue should be fixed once I check in the current version of the Commander. I'll do that now and then send this issue back to you and perhaps you can re-test.
Working now.