The RTI_BRW_GenerateReport routine has an overrideListID argument. We've noticed that if the name of the savelist has a space in it this causes problems for the BRW, at least with programmatic data sources. Instead of seeing the query appear with a valid syntax like this:
WITH KEY = "MyKey"We see:
0 = 1This is also the same result if we pass in a non-existent savelist name. I suspect the space is causing a parsing problem on the backend and an invalid savelist ID is created.
This is with OI 9.4. Haven't tested with OI 10.
The RTI_BRW_GenerateReport routine has an overrideListID argument. We've noticed that if the name of the savelist has a space in it this causes problems for the BRW, at least with programmatic data sources. Instead of seeing the query appear with a valid syntax like this:
WITH KEY = "MyKey"We see:
0 = 1This is also the same result if we pass in a non-existent savelist name. I suspect the space is causing a parsing problem on the backend and an invalid savelist ID is created.
This is with OI 9.4. Haven't tested with OI 10.
Hi, Don. I haven't looked into this yet, but I do recall that when a savelist name has a space in it, we treat it as <filename><space><listname> - that is, we allow you to save and restore the savelist from a table other than SYSLISTS. That's possibly why the list isn't getting found (and saved?) - the "first word", which is expected to be the table name, probably doesn't exist as a valid table…?
- Bryan Shumsky
The RTI_BRW_GenerateReport routine has an overrideListID argument. We've noticed that if the name of the savelist has a space in it this causes problems for the BRW, at least with programmatic data sources. Instead of seeing the query appear with a valid syntax like this:
WITH KEY = "MyKey"We see:
0 = 1This is also the same result if we pass in a non-existent savelist name. I suspect the space is causing a parsing problem on the backend and an invalid savelist ID is created.
This is with OI 9.4. Haven't tested with OI 10.
Hi, Don. I haven't looked into this yet, but I do recall that when a savelist name has a space in it, we treat it as <filename><space><listname> - that is, we allow you to save and restore the savelist from a table other than SYSLISTS. That's possibly why the list isn't getting found (and saved?) - the "first word", which is expected to be the table name, probably doesn't exist as a valid table…?
- Bryan Shumsky
Hi Bryan - Perhaps that is the issue but I can't even get that to work with a SYSLISTS key without a space. That is, if I pass in "SYSLISTS <savelist>" and <savelist> has no space, it isn't pulling from the savelist.