Support custom values
See original GitHub issueI could be reading the setup wrong, but it appears the only way the Y axis value is determined is by the number of records returned in the results. It would be nice to set the value used for y axis in the query itself. For example, if we wanted to see number of users by role we would currently query like this:
SELECT role_name FROM users
It would be nice to offload this to the SQL like this:
SELECT role_name, count(*) as y_axis
This allows for more custom/advanced charts.
Is this already supported and I’m just missing it in the docs?
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Custom Values / Merge Fields - HighLevel Support Portal
Custom Values / Merge Fields Print Note: Now that Workflows are live in all accounts, you can do everything that Triggers and Campaigns...
Read more >How to use: Custom Values | Zapier University 102
See how custom values give you more flexibility when working with fields.
Read more >What are Custom Values? | Help Center - Automate.io
1. In the List/Audience field, click the drop-down button. Click '- Use Custom Value -'. A field with the name 'List/Audience ID' appears...
Read more >Custom Fields VS Custom Values on Go HighLevel - YouTube
For a Free Trial of $297 Agency Unlimited GoHighLevel* Plan and to get my Support Portal Snapshot as a bonus.
Read more >Adding custom fields to your tickets and support request form
Creating custom ticket fields · Enter Field options to include in the list. Click the X to remove a value. · Click Sort...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Just a quick update that this feature is being worked on in #57
Not planning to add field selection through the SQL query just yet. Will have to experiment with that after the new updates
Using
count(*)
may have not been the best example because the count also returns the number of records. What I’m hoping for is to set the y-axis value in the SQL itself. A better example might be to use anAVG
,SUM
, or even an existing column.The “setup the fields” page is effectively selecting the column to use on the x-axis, with the y-axis being the count of instances for that column. The ability select a column that overrides the y-axis drastically increases what these charts can visualize.