Very helpful, thanks! After some playing around I found that adding the Unit field is not necessary. When you go to the "group by" step and add an aggregation, simply choose "Count" instead of using "Sum".
Greg, in your chart tutorial back from 2021, when "doing the search for" "Starting Date" you are enabling the "Sort By" option with "Descending" "No" to get the first item from the search list. (ordering the list by date within the search itself) Here at 18:40 you did not choose the sort option, just curious why ?
This is expected UX as there is no information to show without data. If you'd like to keep the chart in place without rendering information, you can create some placeholder rows of data in the DB with date stamps and values of 0. You'll need some conditional logic to load this data when there is no real data to show.
You could also set the default value for UNIT to 1 and all applications created after that would contain 1. One less step in the workflow... makes sense?
That's what I was thinking too. But then I wonder if it makes any difference in the performance of app. If not, then having the step in the workflow makes more sense in terms of explicit documentation.
Lesson 7.4 covers downloading the CV. I didn't include status updates in the end but this is easy to create in a workflow step, just update the status field.
Very helpful, thanks! After some playing around I found that adding the Unit field is not necessary. When you go to the "group by" step and add an aggregation, simply choose "Count" instead of using "Sum".
My chart isn't showing data and I've followed all the steps, how do I fix this?
Greg, in your chart tutorial back from 2021, when "doing the search for" "Starting Date" you are enabling the "Sort By" option with "Descending" "No" to get the first item from the search list. (ordering the list by date within the search itself)
Here at 18:40 you did not choose the sort option, just curious why ?
The default sort order for returned data is ascending. So we can just leave it blank in this instance.
@@gregory-john all the nuances, thanks Greg !
Shall we also add a "unit" field for "user" data type if we want to analyze user data? (Like the example, application data type here).
Fantastic session ! Just what I needed for my dashboard.
can you change "Created Date" manually in the database?
When theres no data the chart dissappears how can i keep it visible and show sum type of data
This is expected UX as there is no information to show without data. If you'd like to keep the chart in place without rendering information, you can create some placeholder rows of data in the DB with date stamps and values of 0. You'll need some conditional logic to load this data when there is no real data to show.
You could also set the default value for UNIT to 1 and all applications created after that would contain 1. One less step in the workflow... makes sense?
That's what I was thinking too. But then I wonder if it makes any difference in the performance of app. If not, then having the step in the workflow makes more sense in terms of explicit documentation.
Yes that works as well.
@EduardoZornoff I've just watched this video and I thought the same.... Why @gregory-john didn`t use count? 🙃😅
i can't find the tutorial when hana has viewed the CV of the candidate and it shows status in candidate dashboard, did i miss something here
Lesson 7.4 covers downloading the CV. I didn't include status updates in the end but this is easy to create in a workflow step, just update the status field.
Whenever i try to login with email it doesn't login and says "This email is already in use" what might be wrong?
wrong password is most likely. You can always try and 'run as' from the user database
looks like Bubble took down all of their own plugins (except one)