Closed Rollpan89 closed 3 years ago
An update: the filter no longer works as well. The list updates when selecting a filter, but no changes in the list is seen. Seems to be the same issue as described above.
Hey @Rollpan89 which version are you using? mind updating to the latest?
Hey @TimGeyssens I've updated to version 3.1.14 and I'm still having trouble with the search function.
The error with the filters seems to have moved to my "readable" fields (key value pair) where it doesn't recognize my ignored field.
E.g for the filter issue:
System.Data.SqlClient.SqlException: Invalid column name 'SchoolReadable'.
---
[UIOMaticListViewField(Name = "Skola")]
[UIOMaticField(Name = "Skola")]
[Column("SchoolType")]
[NullSetting(NullSetting = NullSettings.Null)]
public string School { get; set; }
[Ignore]
[UIOMaticListViewFilter(Name = "Skola")]
public string SchoolReadable => MemberEducationCategories.GetAllSchools(School).ToString(); // <- GetAllSchools() = Dictionary<string, string>
The issue with the search function seems to be the same though.
yeah you can't use UIOMaticListViewFilter on a non db field... since it will build a db query... and it isn't a column...
Alright! That makes sense!
However, the main issue still persists with the search function I'm afraid.
odd, in all browers?
Yeah. I've tried all browsers. The values I'm searching for is all in the db
An update: since the project is near its deadline we decided to override all the filtering and search functionality with our own logic, so the issue is no longer critical. I guess the issue was local for our environment so no further action needed for our part in this ticket.
Hey guys!
I've been having trouble with the searchbar with my UIOMaticFields. I keep getting no results no matter what I search for. The filters work as intended, but the searchbar is important.
So i dug around and found that the getPaged() function returns this URL:
/umbraco/backoffice/UIOMatic/Object/GetPaged?typeAlias=people&itemsPerPage=40&pageNumber=1&sortColumn=&sortOrder=asc&filters=&searchTerm=
which in turn returns HTTP error 417. Not sure if it's correlated or not.My code looks something like this