nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Database embed alternative default view shows as blank

Olie Ryan-George

Hi everyone,

When I embed a database and select a default view that isn't "All Entries", I get "No matching entries found".

I then have to move it to "All Entries" and then move it back again to get the data to show. This is not very usable.

Can we have a fix for this?

See the image below showing the difference between when I've got the alternative default view (top) compared to when I had "All Entries" as the default view and changed to the other view (bottom).

Thanks,

Olie

Comments

Rachel Li

Hi @Olie Ryan-George thanks for reporting this! Could you share some more information about the view settings (i.e. filters, sorting, hidden fields, layout) you're using for the views that are showing "No matching entries found"?

Olie Ryan-George

Hi Rachel,

Here are screenshots of the settings for both. They are identical. Sort is none and layout is table. I've also added the full table at the bottom. Thanks!

Rachel Li

Thanks for sending over these screenshots! We’re aware of an issue where views with “contains” filters on linked fields (ex. entry link, entry details, page link) will not show any entries on initial load. It looks like this is the same issue that the you're experiencing since you're using a "contains" filter on a Page link column ("Data Model"). We’re looking into it and are hoping to have a fix for it soon!

Could you confirm that this issue doesn't happen for other types of filters? For example, if you get rid of the Data Model filter and just filter by API Input Type.

Olie Ryan-George

Hi Rachel,

Yes, you're correct. If I do exactly the same but for a view which just has an "is string type" filter. This issue doesn't occur.

Please keep me updated on the fix!

Melina Torres

Hi, where can I find a solution for this? I am experiencing the same issue of "No matching entries found" in a database of 100 rows for my Atlassian Cloud instance.

Rachel Li

Hey @Melina Torres we have 2 open JAC tickets related to this issue, can you verify if your case falls under one of these?

Melina Torres

Yes, it is 82114

It was opened by Edson, who tried to help me fix the issue, but there is still no solution. How does it work for Olie, and what is the solution?

Rachel Li

@Melina Torres I believe the issue reported by Olie was for "contains" filters on Page Link fields. We fixed his issue over a year ago. 82114 is referring to fields that are dependent on other linked fields like Jira issue details or page details, so it could be different from Olie's issue or the behavior has regressed since then (it's been a year, and we've made many changes to databases since then).

We are working to get this bug prioritized and completed within the team. For now, you can use the workarounds outlined in the JAC ticket. If you have any more details on the issue you're experiencing please feel free to share with us on the JAC ticket, as it can help us with the bug fix!

Welcome!

It looks like you're new here. Sign in or register to get started.