Open network console and fire a query and notice changes in the network console.
SAQL tester github. The first link is the SAQL tester.
Drag the salesforce analytics cloud SAQL tester to the bookmark. If it asks you to be logged in to be able to access the bookmark, your bookmark is installed properly.
You can paste the code on the SAQL editor and see the data tables in the output column.
Biggest difference between SAQL and SQL you need a generate statement to get an output, else an error would pop up. Reason is that it is quering a non relational database much like Apache Pig™.
Product documentation gives more context on SAQL.
Steps in the JSON are generally powered by the compact form. To power using SAQL you need to go to the Network Console and copy the Request payload source.
You get a JSON payload on the POST command which is sent from the client to the server.
To power the JSON by SAQL you need to add a command "pigql" and add the query in the query block. The legacy name for SAQL is pigql.
When the query is now run it is powered by the pigql/SAQL step but the same dashboard is seen. When the pigql/SAQL is present, only this is fired and the compact form is not being run.
The compact form parameters are still needed at this point in time like measures, groups and filters even though its being passed by SAQL.
How do I know that the piqgl/SAQL is taking precedence over the compact form?
Choose the limit value to something else you will notice that the SAQL will run when you add that change in the JSON dashboard.
No comments:
Post a Comment