Backendless Table Whereclause and search

Bug
1

Hi Team,

Have come across a glitch when using a UI Builder backendless table, if you use whereclause logic and then try use the search function you get errors as follow.

sdk.js:16 Uncaught (in promise) p: Where clause ‘(ownerId = ‘127A500D-4A03-4CD5-8AB3-F2E6EEB53DAA’) AND (Registration like ‘%Ford%’ or ID like ‘%Ford%’ or Odometer like ‘%Ford%’ or Make like ‘%Ford%’ or Model like ‘%Ford%’ or Year like ‘%Ford%’ or VIN like ‘%Ford%’ or Engine_Number like ‘%Ford%’ or Tare like ‘%Ford%’ or Tank_Capacity like ‘%Ford%’ or Service_Interval like ‘%Ford%’ or Service_Warning_Duration_in_KM like ‘%Ford%’ or Can Max Pedal like ‘%Ford%’ or Can Max RPM like ‘%Ford%’ or Can Max Speed like ‘%Ford%’ or Can Max Temp like ‘%Ford%’ or Instalment like ‘%Ford%’ or Depreciation like ‘%Ford%’ or Insurance_Premium like ‘%Ford%’ or Tracking like ‘%Ford%’ or Annual_License_Fee like ‘%Ford%’ or Fixed_Maintenance_Plan_Cost like ‘%Ford%’ or Fixed_Monthly_Sundry_Cost like ‘%Ford%’ or Warehouse like ‘%Ford%’ or Commission_Rate like ‘%Ford%’ or Ideal_Fuel_Consumption like ‘%Ford%’ or Ideal_Rate_Per_Km like ‘%Ford%’ or Ideal_Rate_Per_Tonne like ‘%Ford%’ or Maintenance_Plan_Rate_per_Km like ‘%Ford%’ or Monthly_Mileage_Target like ‘%Ford%’ or Monthly_Profit_Target like ‘%Ford%’ or Monthly_Tonnage_Target like ‘%Ford%’ or Payload_Override like ‘%Ford%’ or Price like ‘%Ford%’)’ is invalid
at k (https://victorrose.backendless.app/api/files/ui-builder/library/sdk/sdk.js:16:672307)

this is obviously just going through each of the table item properties however it return an invalid whereclause.

image
image1630×796 93.9 KB

Is there a work around that you have come across.

Kind Regards,
Raymond

2

Hello, @Raymond_Woodley

It seems that the issue might be caused by the use of curly (typographic) quotes instead of straight quotes. The curly quotes (‘ and ’) are not recognized correctly in SQL queries. Please replace them with straight quotes (') to resolve the issue. Here’s the corrected version:

ownerId = '127A500D-4A03-4CD5-8AB3-F2E6EEB53DAA'

Regards,
Serhiy

3

Hi @Serhiy_Melnychuk,

Thank you for your response, the problem still persists, i feel it may be more related to the spaces now allowed in data tables.

Kind Regards,
Raymond

4

Hi Raymond,

Does the where clause work in the REST Console tab on the Data screen in the Backendless Console?

Regards,
Mark

5

Hi @mark-piller,

Thank you for your response the whereclause does not work in REST Console.

Forgive me for pointing out that the “Complex” whereclause is the one generated from the backendless table UI Component when searching, the Whereclause i use is a simple ownerId clause in the whereclause logic.

Kind Regards,
Raymond.

6

@Raymond_Woodley ,

Thank you for clarification. I was able to reproduce the problem. It is caused by columns which has space in their names. UI component does not wrap those column names in “`”.

I have created an internal ticket to fix it.

As temporal solution I can suggest you to replace spaces with underscore in columns names. This will fix the issue.

Sorry for inconvenience.

Regards, Andriy

8

Hi @Andriy_Konoz,

Thank you for your response, sadly i will have to wait for the fix as i have referenced the columns in to many places to rename the columns.

Kind Regards,
Raymond

9

Hi @Raymond_Woodley,

We’ve just updated cloud servers with a fix for the issue you described above. Could you let us know whether the fix works for you?

Regards,
Bohdan