FRM-41214 when calling a report from a form in DS1012

Question

This is weird. I have a report that contains a lexical parameter that is intended to add an "AND" clause to the WHERE so I can use the same report to do an unrestricted query or a restricted query.
To do an unrestricted query, this works fine:
ls_param := 'and_clause='||''||' paramform=no';
SET_REPORT_OBJECT_PROPERTY(repid,REPORT_OTHER,ls_param);
v_rep := RUN_REPORT_OBJECT(repid);
etc. according to all the notes on the matter. The report runs and brings back all rows because the "AND" part of the WHERE is null,
But as soon as I attempt to modify the ls_param variable, the form refuses to run. I am not mis-using the single quotes. I have all the quotes in variables as in:
ls_and_clause := chr(32)||' AND id IN (';
to set the first part of the clause, followed by:
FOR id_rec in id_list LOOP
ls_and_clause := ls_and_clause ||QT||id_rec.id||QT||',';
END LOOP;
where id_list is a cursor that brings back a list of IDs qualified per user, and QT is a variable that holds chr(39).
I have read the notes on being careful not to pass spaces, so everything is concatenated into a single variable that gets passed on the final
SET_REPORT_OBJECT_PROPERTY(repid,REPORT_OTHER,ls_param);
where ls_param includes something like "and_clause = 'AND id in ('901','902') paramform=no"
Seems to me, this should work. Does anyone else have any insight on doing this kind of thing?

Answer 1

Thanks for the toubleshooting tip. It helped me find the problem. For some reason when the AND clause included the table name, the report would not run. But when the AND clause does not include the table name, the report works:
AND table.col IN ('101','102') fails, but
AND col IN ('101','102') works.
Go figure. I just hope I never have to do this when the table name is required to remove ambiguity.