24 Apr 2020 11:33 AM
We have a report that currently uses a Process to call a stored procedure to update a table from inputed data. However we want to get away from using Processes as they seem to be inconsistent. Instead, we've started calling the procedure in-line. I've recently learned that you can't pass inputed data to a procedure's parameters. Instead, some have started to used PopupPanels and Target.IncludeFrameReport elements (which calls another report) to do the updates.
Is this correct? Is there not a way to cleanly pass input data to a procedure's parameters? Everything I see in Logi's support says to use Processes.
28 Apr 2020 01:06 PM
Can you expand on the thought that processes seem to be inconsistent? I do a lot of table updates via process and they seem to work well. I use the process because I'm typically looping through data table records which is only available in the process. I have some stored procedures that returns a data table (rather than using a standard query) and they accept parameters just fine. Do you have a specific example?
28 Apr 2020 03:43 PM
Unfortunately no. I regularly used Processes, but I was told that users would occasionally update data but it woouldn't stick. So I was tasked with rewriting the report without Processes.