Url commands

If the security allows, there are a few commands in the query part (after the ?) that can be used for manipulating how a page is loaded. First of all the an url in DataEase server will be as this. protocol://name.in.dns/path/to/commands:port?dataeasequery&querypart1=val&querypart2=val etc.

So why is this layout important? If you see after the ? you have dataeasequery. This mean if you have a page that do not need a dataease query, you still have to skip it in the query part of the url. So then you url will be http://127.0.0.1:8765/myapp/mypage.html?&json=1

As you see you have to add ?& before you can start with query commands.

List of query commands you can use

=in order A field name to sort on in order. The format is &fieldname=in order& and is added as part of the query commands.
=in reverse A field name to sort on in reverse. The format is &fieldname=in reverse& and is added as part of the query commands.
astext=1 Override header for pages to send the data as text/text instead of text/html or application/json; charset=utf-8
code= Used in testdql or rundql to send the code to test for errors
excludefields=[] A list of fields to exclude. * is supported in field names. Used in data queries to limit the number of fields loaded into the page. The format is: ["fieldname", fildname2","*name","name*"...]
fulltdf=1 Used by DQL to tell if you should expand DQL definition as is before it get cleanup for empty levels.
getbody=1 If the body should be returned in definition of a page
getbodytree=1 If the compiled version of the body should be listed in the page definition
getcode=1 If the code part should be listed in a page definition
getdefinition=1 Generate definitions for dql and tables used in the page
getrecordcount=1 Return how many rows was found in the the main table view used in the query
getrelationnames=1 Return relations together with table definition when doing /definition/table/tablename
json=1 Show the data generated in the page as json instead of generating the page text. This can be useful for seeing what is coming out your dql or data queries in the page. It will also show the errors in a dql if you have any.
jsonpretty=1 Make the json generated human readable by adding line feeds and spacing.
includefields=[] A list of fields to include. * is supported in field names. Used in data queries to limit the number of fields loaded into the page. The format is: ["fieldname", fildname2","*name","name*"...]
match= Used by list files to match files. You can use name*, *part* or na?me.* etc. 
noqueryallowed=1 Allow no dataease query for this query. To avoid problems where you get first record because of wrong query, the server expects all connect for reading and writing data to be done with a proper query. This is added to override this if you really need to do data read or write without using a query, and by adding this, you know that it is this you do.
showhidden=1 Used by listtables and listinternals to allow system tables in the list.
usetemplate= If you are a user with level high, you can use this to switch to another template on a page.
Ex ?&usetemplate=/templates/basetemplate.html will use the base template instead of what is set in the page.