Triggering a label print (.rpl layout) via a PL/SQL-based deferred call fails with 'PluginExecute Failed. null,' while the exact same PL/SQL flow works fine when the layout is a regular report (.rdl) instead — what's different about triggering an .rpl label layout this way?

Q: Triggering a label print (.rpl layout) via a PL/SQL-based deferred call fails with 'PluginExecute Failed. null,' while the exact same PL/SQL flow works fine when the layout is a regular report (.rdl) instead — what's different about triggering an .rpl label layout this way?

Add an 'OPTIONS' attribute (e.g. Client_SYS.Add_To_Attr('OPTIONS', 'COPIES(1)', tmp_attr_)) to the print job's attribute string before calling Print_Job_Contents_API.New_Instance, specifically when the layout being triggered is an .rpl label template — this attribute isn't required for a normal .rdl-based report triggered the same way, but its absence is what causes the plugin-execution failure specifically for .rpl label layouts triggered via this PL/SQL pattern.

Answer

Add an 'OPTIONS' attribute (e.g. Client_SYS.Add_To_Attr('OPTIONS', 'COPIES(1)', tmp_attr_)) to the print job's attribute string before calling Print_Job_Contents_API.New_Instance, specifically when the layout being triggered is an .rpl label template — this attribute isn't required for a normal .rdl-based report triggered the same way, but its absence is what causes the plugin-execution failure specifically for .rpl label layouts triggered via this PL/SQL pattern.

← Browse Reporting and analytics questions