Preview Data not working for SQL with {where} in DA schema modeler

Data Abstract
1

When I click ‘Preview Data’ in the DA schema modeler for a custom SQL containing {Where} we get a request to enter the value for parameter where but regardless of what we enter we can’t get data
error 'an expression of non-boolean type specified in a context wjhere a condition is expected, near ‘@P1’ '
We use the {where} to add custom where clauses.

What is wrong? How can this be solved?
-Frederic

2

Hello

Could you please show your SQL statement (rename the tables used in it if you do not want to disclose their names)?

I’ve just tried a simple statement like

SELECT 	
	"Id", "LastName", "FirstName", 
	"BirthDate", "HireDate", "Job", 
	"Address", "City", "PostalCode", 
	"Country", "HomePhone", "Photo", 
	"Notes" 
FROM 
	"Employees" 
WHERE 
	{WHERE}

and there were no issues previeving it.

3

I believe it is with every query
Below a query with a view but others have it too.
select
t44_primkey,t44_datechanged,t44_userid,t44_tpr_primkey,
t44_prd_cnk,t44_prd_primkey,t44_rizivcode,t44_indicbeste,
t44_datumgeldigheid
from vTar44Actief
where {Where}

DA Schema Modeler V9.2.103.1311
RO DA framework V9.2.103.1311

4

How vTar44Actief is defined on the DB server level?

5

it is a view containing select * from tar44
When I replace vTar44Actief by the table tar44 in the DA schema modeler the problem persists

6

Unfortunately I was not able to reprodice the issue. Please send to support@ the following info:

  1. daSchema file containing failing table
  2. DDL for the table(s) used in the statement
  3. Error screenshot
  4. Exact DA version #

Thanks in advance

7

You’ll find the requested files in the attachment

daissue.zip (72.2 KB)

The version is
DA Schema Modeler V9.2.103.1311
RO DA framework V9.2.103.1311

8

I think it hase to be full uppercase {WHERE}. {Where} used to work for me in previous DA versions but not anymore. I don’t know why, they must have changed something.

9

Thanks, logged as bugs://78895

10

Please use {WHERE} macro in proper case. I’ve logged an issue to handle other cases ofthis macro as well.

Sorry for the inconvenience

11

bugs://78895 got closed with status fixed.

12

Fix will be available in the next Beta build