I am getting the same error: Could not create widget DataGridColumnSearch.widget.DataGridColumnSearc,
While using the date as a column in Datagrid for the 8.4.2 version

Date search is not working properly when entity localization is NO .
Suppose I have Entity Student with birthdate attribute of type Date and Time and localization is not enabled. Now consider one student has birthdate 31-08-2020. When I search for 31-08-2020, I do not find above student but when I search 30-08-2020, I can find this student.

I see this issue is fixed when I pass localized attribute value as true in searchObj object of _addDateSearchBox function . I have tested it for both attribute types(localized and non localized) and it seems to be working fine. But I am not sure if this is correct fix.

Mendix version: 7.23.3

so this was working great.. and then suddenly and now consistently when i'm using this widget, everything briefly appears like normal, then all of the data disappears. back/forward paging buttons widget shows like 1-20 of 36 or whatever, but there is no data shown. DGCS widget filter controls are there but don't seem to do anything to reappear any portion of the list. this is versus a microflow that returns a list of entities with several enum attribs. i verified that the microflow was returning many entities.

thank you for any assistance.

The widget appears not to be working on mobile devices. Tested it on Android and Apple mobile devices, but it did not work in all the test setups.

Only way to make it work is to load the desktop version, in browser that support this option.

Mendix runtime showed "Could not create widget DataGridColumnSearch.widget.DataGridColumnSearch" on page.

No error message shown in console. Modeler version 7.23.3.

The used .includes() is not support in IE. Possible solution is noted here:

https://stackoverflow.com/questions/36574351/includes-not-working-in-internet-explorer

Hey,

Quick idea--not sure if it makes sense at part of this widget or as a separate one--but it would be cool if we could add "toggles" for pre-defined filters to a data-grid. I.e. instead of having separate xpath grids on different tabs (for "My things" and "All things", for example) we could have buttons for All and Mine that would apply an xpath constraint using datasource.setConstraints(/* some xpath */); maybe where the xpath is defined in the modeler?

Thoughts? It would save us from having to duplicate data grids when we want different filters of the data

Message is: Could not create widget DataGridColumnSearch.widget.DataGridColumnSearch

error:Could not create widget DataGridColumnSearch.widget.DataGridColumnSearch
GRID Entity: GWSAMPLE_BASIC.SalesOrder

where the grid is showing a list of GWSAMPLE_BASIC. SalesOrder

Hi Tieniber,
I call a datasource by a microflow.
i have added the widget below grid.
when a grid is called 1st time i get all data..
but when a grid is called 2nd time data comes and disappears.
do we have a work around or something for this ?

When using the widget in grids on tabpages, all the data is loaded when opening this page, this will make it very slow. The standard functionality of mendix is to load the data of the tabpage when opening the tab.

This 'Lazy loading' functionality would be a great adjustement to the widget.

Eric,
Will you be able to update this widget to work with the latest versions of Mendix? I am getting ready to upgrade and app and figuring out if I will need to remove this widget.
Thanks,
Mike

When fields are not found, the return of empty values is not checked for valid returns. I.e. in _addEnumSearchBox ()

the following code is used:
if (mx.meta) {
enumMap = mx.meta.getEntity(columnEntity).getEnumMap(columnAttribute); //used in 6.10.3
} else {
enumMap = mx.metadata.getEntity(columnEntity).getEnumMap(columnAttribute); //used in 5.20
}

I am using 6.5.1 modeler and from testing mx.meta is used, however the enum is not found and returns null.
However, the code does not check for null values and as a result the script hangs.

I added the following after the code above, which workes around the issue (by not placing a search box) but the real issue obviously is that the enum is not found in 651

		if (!enumMap)
		{
			return;
		}

Think in general it is a good idea to check return values if used further down the code.

ERROR: function mx_tolocaldatetime(timestamp without time zone, unknown) does not exist

Implementation in Mx 8.17.0.11170 unfortunately gives error "Could not create widget DataGridColumnSearch.widget.DataGridColumnSearch".

Getting the error "window.mx.parser.delocalizeEpoch is not a function TypeError: window.mx.parser.delocalizeEpoch is not a function" when searching on date fields.

When I have the widget in a tab that is set to refresh, each time I click on the tab (without refreshing the page), the widget duplicates itself. See screenshot:

In thinking about it, I don't really need to have that tab set to refresh since it is a dynamic search, but wanted to raise the issue.

When searching on a boolean value, the selectable options are in English (Yes/No). It would be nice if the selectable options would be based on the users' language as defined in his/hers account.

Searching in a DataGrid with columns which are populated over association does not work. Problem lies in the fact that it fires a 'contain' on the id in the association table instead of in the table of the actual associated entity. Error: 'java.lang.IllegalArgumentException: Global identifier should be a number'.

Hi,

Scenario:

• User put some value in filter.
• number of results is bigger then one page of datagrid
• user jumps to next page of results in datagrid
• next page shows all results and don't use value from filter

It's possible to fix that?

ps. Great work, great widget! Definetly should be not extension but standard functionality in Mendix.
regards

I added the widget to a Mx9 project, but is does not work. The searchfields are shown correctly in the browser, but it does not execute a search when I enter a search string.