Kanbas isn’t displaying the whole row items, maybe it’s a setting I did wrong. I’m sure it’s a quick fix but I’ve been on it for a while now and would appreciate your help.
Here’s a video addressing the issue:
[https://youtu.be/EtJ3FqqE3GQ]
What if you just don’t set the limit at all?
Not sure if it’s an issue, but your “save order” column should not be writing to the “Date” column if I understand you right.
Hello I’m here again… haha (very sorry)
After a while staring on a new app the same issue arose again.
What if you assign a user-specific text column to the “Save order” field?
Also, why do you have this filter?
The filter there is created automatically it what shows the amount on the kanban…
Also for the user specific column you mentioned for the save order how would that work? Should I create a new column or I’m assigning it to an existing one?
Just create a new column called “Order”, make it user-specific and assign it to the user-specific text column.
If it doesn’t work as well, and if you don’t mind, please send your team’s invitation link privately to me so I can look at the issue in the builder.
I didn’t quite get the idea of the user-specific text column “How do I assign it to the other”
I’ve sent the link, thank you so much for taking the time to check it
I joined the team, and whilst your way to deal with dates is not ideal, I can’t find out why the Kanban component doesn’t work.
I tried a list collection pointing to the same query and it works normally. I’m thinking it’s a bug, and you should chat to the team using the Intercom integration (bottom right bubble) to deal with this.
1 Like
Alright thank you so much I just recently started with glide about a month ago… I really appreciate it. Actually I’m happy you got to see my backend… haha is there a source I can read up more on using the dates (I’ve read it from the glide docs)
As for the kanban section I’ll let the glide team know but since the list component works fine I’ll use that.
Thank you so much
1 Like
Thank you you’re so kind. I haven’t had the time today to write out about best practices of dealing with dates, but one problem you had was that you used the sole month to create the relations/queries. It will be problematic when it comes to next year, and the relations/queries return both Jun 2024 and Jun 2025 records. You should factor in the year as well.
1 Like
Yes, adding a year is part of the system but that looks really complicated right now as months was harder to create than the date system… I’ll look into it though. Thank you. I’ll work on it.
Here’s a great thread for you. Don’t hesitate asking questions, and let us know how the talk with support goes.
Thank you, already read it and found my own case… I didn’t relate some columns to a date string… will read up more. Thanks.
Also unless I’m on the paid plan before I can talk to the team… haha
Ah yes, you’re on a Free plan. If the issue keeps happening please let me know and I’ll try to send it to the team.
Awesome thank you so much.
I’ll wait for a few more days and get back to you.
1 Like