Data View filter not showing proper values in Expression Builder

kfawcett · February 20, 2024, 10:41pm

Wappler Version: 6.2.1 Beta
Operating System: Windows 11
Server Model: Capactior
Database Type: SQLite

Expected behavior

The structure from the Data Source should be available in the Expression editor

I should see these columns as values based on the Data Source selected.

Actual behavior

No structure/fields from the Data Source are shown. I only see these values.

How to reproduce

Create a Page Flow that has a SQLite Query
Create a Data View that uses the query from the Page Flow as the data source
Try to create a Filter using fields from the query

kfawcett · February 27, 2024, 12:49pm

Bumping for assignment.

George · February 29, 2024, 8:59am

I tried to replicate your problem, but it was all working fine to me. I could see the query fields in the data view data source binding and pick them later on as filter.

Please restart Wappler with logging, reproduce the problem and attach the debug log. See:

George · February 29, 2024, 9:24am

Also are you on the stable of beta extensions channel?

Make sure you are on the beta channel and use the latest Wappler

kfawcett · February 29, 2024, 12:07pm

The new Expression Builder is only in Beta channel. Logs attached.

wappler.zip (2.9 KB)

Another side effect is it wipes out existing expressions.

kfawcett · February 29, 2024, 6:17pm

I’m getting a slightly different error after upgrading to v6.3.1 in Terminal.

RulesParseError: Incorrect data object passed 
at h.error (file:///C:/Users/Keith/AppData/Local/Wappler/resources/app/Shared/DMXzone/dmxAppCreator/UI/queryBuilder/js/query-builder.standalone.min.js:7:41529) 
at c.setRules (file:///C:/Users/Keith/AppData/Local/Wappler/resources/app/Shared/DMXzone/dmxAppCreator/UI/queryBuilder/js/query-builder.standalone.min.js:7:25326) 
at $.fn.queryBuilder (file:///C:/Users/Keith/AppData/Local/Wappler/resources/app/Shared/DMXzone/dmxAppCreator/UI/queryBuilder/js/query-builder.standalone.min.js:7:47260) 
at initQueryBuilder (file:///C:/Users/Keith/AppData/Local/Wappler/resources/app/Shared/DMXzone/dmxAppCreator/UI/dmxAppConnect/expression.htm?theme=dark&app=true&noinit=true:1178:17) 
at initUI (file:///C:/Users/Keith/AppData/Local/Wappler/resources/app/Shared/DMXzone/dmxAppCreator/UI/dmxAppConnect/expression.htm?theme=dark&app=true&noinit=true:661:5) 
at file:///C:/Users/Keith/AppData/Local/Wappler/resources/app/Shared/DMXzone/dmxAppCreator/dmxDWApiBridge/dmxNWApiBridge.js:7:24962

George · February 29, 2024, 6:38pm

Seems to be specifically related to the data types you have in your SQLite query.

What database types are the columns you have there?

kfawcett · February 29, 2024, 7:33pm

Really basic types on this table.

kfawcett · February 29, 2024, 9:53pm

What does this in the logs mean?

[2024-02-29 07:00:31.468] no meta found for UserLabels in [
  {
    "sub": [
      {
        "type": "text",
        "name": "LabelId"
      },
      {
        "type": "text",
        "name": "Name"
      },
      {
        "type": "text",
        "name": "MessageListVisibility"
      },
      {
        "type": "text",
        "name": "LabelListVisibility"
      },
      {
        "type": "text",
        "name": "Type"
      },
      {
        "type": "number",
        "name": "MessagesTotal"
      },
      {
        "type": "number",
        "name": "MessagesUnread"
      },
      {
        "type": "number",
        "name": "ThreadsTotal"
      },
      {
        "type": "number",
        "name": "ThreadsUnread"
      },
      {
        "type": "text",
        "name": "TextColor"
      },
      {
        "type": "text",
        "name": "BackgroundColor"
      }
    ],
    "name": "query",
    "type": "array"
  }
]
[2024-02-29 07:00:31.469] _findActionStepFromExpression: ERROR PARSING: UserLabels.data.query: UserLabels is not defined
[2024-02-29 07:00:31.469] getRulePropertyDataExpressionSchema: No meta found for UserLabels.data.query with in base: 
[2024-02-29 07:00:31.474] OPEN popup: PopupWindow_1709208031473

George · February 29, 2024, 10:31pm

Seems like the output meta data for the page flow can’t be found.

Could you check in dmxAppConnect/config.js under your page app id and then the page flow id, see what data is defined there? You can paste it here.

kfawcett · March 1, 2024, 2:57am

"UserLabels": {
      "meta": [
        {
          "sub": [
            {
              "type": "text",
              "name": "LabelId"
            },
            {
              "type": "text",
              "name": "Name"
            },
            {
              "type": "text",
              "name": "MessageListVisibility"
            },
            {
              "type": "text",
              "name": "LabelListVisibility"
            },
            {
              "type": "text",
              "name": "Type"
            },
            {
              "type": "number",
              "name": "MessagesTotal"
            },
            {
              "type": "number",
              "name": "MessagesUnread"
            },
            {
              "type": "number",
              "name": "ThreadsTotal"
            },
            {
              "type": "number",
              "name": "ThreadsUnread"
            },
            {
              "type": "text",
              "name": "TextColor"
            },
            {
              "type": "text",
              "name": "BackgroundColor"
            }
          ],
          "name": "query",
          "type": "array"
        }
      ],
      "local": {}
    },

kfawcett · March 1, 2024, 2:48pm

So I created a brand new page flow that’s exactly the same as the UserLabels page flow. The meta in config.js looks exactly the same, but this one doesn’t have an issue, so there must be some other reference that’s causing the filter to not work.

"UserLabelsRedo": {
      "meta": [
        {
          "sub": [
            {
              "type": "text",
              "name": "LabelId"
            },
            {
              "type": "text",
              "name": "Name"
            },
            {
              "type": "text",
              "name": "MessageListVisibility"
            },
            {
              "type": "text",
              "name": "LabelListVisibility"
            },
            {
              "type": "text",
              "name": "Type"
            },
            {
              "type": "number",
              "name": "MessagesTotal"
            },
            {
              "type": "number",
              "name": "MessagesUnread"
            },
            {
              "type": "number",
              "name": "ThreadsTotal"
            },
            {
              "type": "number",
              "name": "ThreadsUnread"
            },
            {
              "type": "text",
              "name": "TextColor"
            },
            {
              "type": "text",
              "name": "BackgroundColor"
            }
          ],
          "name": "query",
          "type": "array"
        }
      ],
      "local": {}
    },

kfawcett · March 1, 2024, 3:00pm

I just ran into a Wappler crash while troubleshooting – used automated reporting to report it. As a result it wiped out the config.js file.

George · March 1, 2024, 3:40pm

the expression parsing will be fixed in the next update - but it was also related to the metadata from your query as it was no longer available. Might all be due to the missing config.js file.

When exactly did it went empty - what kind of crash you got - what was the last thing you saw or did?

kfawcett · March 1, 2024, 4:28pm

I was changing the data source and saving when Wappler crashed. Prior to that the config.js showed all values as shown in the git compare.

It looks like this issue is related to the Data View component’s meta. It appears that is not writing its meta to the config.js in some instances.

I do a lot of editing through code view. I’ve also renamed components and duplicated them. So one or both of these actions appear to not update the config.js file. It’s only when I use the UI to update the Data Source that the meta is updated in config.js.

Is it possible for Wappler to watch the page file and update config.js on modification or on save? I mention this because I’m also seeing a lot of unnecessary items in config.js due to removing, renaming, and/or other actions that make certain meta data no longer necessary.

George · March 1, 2024, 4:57pm

Could explain that more in detail with screenshots?

kfawcett · March 1, 2024, 5:06pm

I think this is all I did, but cannot be 100% certain.

I clicked on lightening bolt.
I changed the Data Source to another Page Flow Data Query
Then I think I clicked CTRL+S to save

Teodor · March 7, 2024, 1:39pm

This should be fixed in Wappler 6.3.2