My question is as given in the Title. Is there any way, to show different dates from the same object in the calendar. Until now, the only way was to add a calendar for every date. I got more than 15 Date in one of my Objects and I need like 5 of them to show in a Calendar. Someone got an Idea? I don't think there is any other Option than using JS, so can this maybe be also a future Request?
Nevermind, Support already told me, that until now it's not possible. For everyone seeing this Topic and hoping to find something. The only Way to have a "better calendar" is by integrating Zapier (for free) and fusing your google calendar with knack. There are many tuts out there how to do it.
No sorry I explained it really bad. I mean that i want to have the possibility to display different datefields in ONE Calendar, but somehow I couldn't find a Solution.
Hi Lorenz -
Please do send in a note on this to email@example.com so we can best help you with your workflow!
But, if I'm understanding your needs correctly here, you'd need to add "Event" records for each of your dates that you want to show in your calendar view.
Or if the event repeats on a regular schedule, you can enable the "Calendar Options" on your date/time field that is used in the calendar, and only have one "Event" record with multiple dates.Data Source filters or other view filters to restrict which records are displayed in the Live App.
I have the same question, is it possible to display multiple date fields from a single object, on a page, in a calendar view? I am only seeing an option to display one date field in a calendar view.
For instance, I have a customer that I call on 1/1/22, I need to schedule to call them back on 1/3/22, then perhaps 1/15/22. Each of these call back dates are entered into a different field in the object since the number of days between calls will vary on a customer by customer basis and cannot be set on a standard repeat. I would like all calls that I have to complete, on any given day, to be displayed in the same calendar.
Hi @Keri - I would refer you to the response above by Laura. It would be a much better database design anyway to have your calls scheduled in multiple “child” records linked to the main object.
Having all these follow up dates in the main object is very much the ‘spreadsheet’ way of doing things but in a relational database you have much more flexibility to connect thins up. For example, with this approach you can have a table displayed with all of the integrations with your customer - some of which will be planned interactions in the future. This makes is easier to see progress, easier to accommodate any number of interactions etc.
You may find my articles about “Relating to Relational Databases” helpful in this regard also - these particular posts are not Knack based but the principles are the same - and my blog also contains a lot of Knack articles which you. may find useful.
Hope this helps.