Currently when using the filter view keyword FIELD, after the filter is merged, it is changed to a CONST. As of v5.6, CONST filters no longer allow filter operators (like | and &).
Expected / new behavior:
Add a new keyword called FILTERFIELD, then after the filter is merged, change it to a FILTER.
Minimal reproduction of the problem with instructions:
paulfisher53
commented
6 years ago
I'm submitting a ...
Current behavior:
Currently when using the filter view keyword FIELD, after the filter is merged, it is changed to a CONST. As of v5.6, CONST filters no longer allow filter operators (like | and &).
Expected / new behavior:
Add a new keyword called FILTERFIELD, then after the filter is merged, change it to a FILTER.
Minimal reproduction of the problem with instructions:
N/A
Liveapp version: 5.6
Browser: all
Anything else: