This mission includes an demo video. Here are the specs:
At the end of the video, the final results look like this:
And here are my results:
This is my REST statement URL: My REST Statement
…48199200/14FAC9EE-9B3C-4F55-9EDD-F57F8C3B0847/data/Country?
property=Continent&property=Count(Continent) as CountryCount,
MIN(LifeExpectancy) as MinLifeExpectancy,
MAX(LifeExpectancy)as MaxLifeExpectancy
&groupBy=Continent
&where=IndepYear>1900
Looks good to me! Any idea why my this Mission isn’t catching and being marked complete?
https://api.backendless.com/CAA21524-8666-2BDF-FF58-C3E148199200/14FAC9EE-9B3C-4F55-9EDD-F57F8C3B0847/data/Country?property=Continent&property=Count(Continent)as CountryCount,MIN(LifeExpectancy) as MinLifeExpectancy,MAX(LifeExpectancy) as MaxLifeExpectancy&groupBy=Continent&where=IndepYear>1900
That URL was constructed both manually and with the NEW Aggregate Functions option in the REST console. Most of it was solved there, but I couldn’t get the MIN & MAX properties to work correctly, so I added them manually. While we’re on the subject, I’m just curious, what would be the correct way to add the MIN & MAX properties?
In these example the MIN function is entered exactly the same way as it was in the REST statement, but still generates an error.
you have incorrect value in Having clause. You can not use as statement there, only logical expressions are available like in where clause. You should construct some thing like the following:
Detailed description of the params and compared against the requirements of the task.
Rest API
table Country -> data/Country
Grouped by Continent column -> &groupBy=Continent
following aggregate function:
count of countries in each continent named as CountryCount -> COUNT(objectId) %20as%20CountryCount
Minimum life expectancy with property name MinLifeExpectancy -> MIN(LifeExpectancy)%20as%20MinLifeExpectancy
Continent property included in request and response
What is wrong here? I’ve noticed that in the Video there is also MaxLifeExpectancy and IndepYear - but its not required based on the written requirements. Also, there are changes as in video we use props but in REST console we use now property.
All of supported functions are not case-sensitive.
Could you try with different names for count function: COUNT, Count, couNt. All of them should be workable.
We had a bug in the tracking of users actions. So in some cases tracking service required the name of the functions was in upper case. But Backendless API do not have such requirement.
The problem was fixed and the new release will be in a next couple of days.
