I have created Interactive Report based on a table. I want to generate customized column heading using page items to be displayed in UI.
I have Page item P1_ITEM1 (source: "SQL Query returning single row").
I have used above mentioned item in Heading Space in Report Attribute of IR as &P1_ITEM1. for a column.
But when I am running the report, I am getting blank/null headings, no name.
Please help me on this issue.
Oracle DB: 11.2g;
APEX Version: 4.2
I think it's because SQL query for P1_ITEM1 runs after heading of Interactive Report rendering.
Try to move your item before IR region or create PL/SQL process (point - Before Region)
SELECT ...
INTO :P1_ITEM1
FROM ...
WHERE ...;
and reset Source Type for P1_ITEM1 to Static Assignement. I tried both methods, it's working.
APEX 5 example link https://apex.oracle.com/pls/apex/f?p=54028:3:10869386854547::YES but also working on APEX 4.
Related
Good morning, I'm trying to reference an Interactive Grid column in a PL/SQL Code (Dynamic action) by coding in the file the column name in this way: :CODE. APEX PL/SQL editor doesn't throws me any error buy when I render my application, APEX debugger throws me the following error:
ERR-1002: Unable to find item ID for item :CODE in application ...
I tried to remake some configurations in the APEX editor, but all seems OK. I don't uderstand the error origin
Thank you in advance
I tried to make an APEX dynamic action buy it throws me an error
I believe that you can only reference interactive grid columns in dynamic actions on specific interactive grid events OR on change of an interactive grid column. Any other dynamic actions (eg on page load) cannot reference the IG columns.
I tried the following:
Create editable IG on emp table
Create page item P1_ENAME
Create dynamic action on change of ENAME column of IG
Add true action of
type: "Execute Server Side Code"
items to submit: "ENAME"
items to return: "P1_ENAME"
PL/SQL Code:
:P1_ENAME := :ENAME;
Add true action of
type: "Alert"
Message: "Name: &P1_ENAME."
And it works fine.
However, if I create a DA on page load that references :ENAME column then I get the error you encountered.
Im trying to write queries on Azure Workbook so that I can run queries on our logs, which would allow me to drill down and view exactly what the exception message is. While doing so, when I execute a KQL query, on the workbooks, the column values are truncated as shown in picture. I want to be able to see the full error stack in order to troubleshoot the issue. Now I can get the operation_Id from here and then run it in Log Analytics to view full details, but I would like to view everything I need on this single page within Azure WorkBook. Clicking on the column doesn't expand it.
You cannot expand a particular column when you execute a kql query on the workbooks.
If you change the visualization to Text you will be able to see the complete stack error message as show in the below image
There are many ways to do something like this in workbooks, but the grid we use doesn't have the ability to expand a single cell like the logs view does.
As another answer states, you could use the "text" visualization to visualize just one cell (0,0) as a text block, but that only works for once cell queries.
or, in the grid settings you can set the column renderer to be a link for those columns, and have that link open the "cell details" view. that will open up a side pane that shows all the content of the cell in a popup view
or you could pick the "generic details" option which will open a side popup showing the values of all the columns in that row)
or, you can go into advanced settings, and enable the option to export parameters when a row is selected. you can then set it to export specific columns as specific named parameters, and use those parameters downstream to see values in something like a markdown text item in the workbook, or in a subsequent query.
there are examples of things like that documented here: https://github.com/microsoft/Application-Insights-Workbooks/blob/master/Documentation/Interactivity.md
I've been trying to print labels in dynamics AX 2012 r2.
I'm following this link:
http://dynamicsaxtipoftheday.com/2014/04/30/generate-product-bar-code-labels-through-retail
Somehow when I get to the Product label report setup form, there is no reports in the report name dropdown.
See screencast: http://screencast.com/t/KVHAIKZ4cT
I have already deployed the RetailLabel report, (A4Landscape3X5_ItemReport and A4Portrait3X5_ShelfReport)
I have also installed the Retail Components.
Does anyone have an idea on how to get the report to show in the dropdown?
Thanks,
The lookup queries the system table UtilElements with the conditions name == 'RetailLabel*' and recordType == UtilElementType::OutputTool. Make sure the UtilElements table contains records for these conditions. The elements are output menu items called RetailLabelA4Landscape3x5_Item and RetailLabelA4Protrait3x5_Shelf. Also make sure that configuration key RetailHeadquarters is activated. I tested the lookup successfully on a AX 2012 R2 CU7 system.
I was able to fix this by modifying the query used in populating the dropdown list.
I'm currently working on an ASP.Net WebForms application that allows a user to select an item from a list, which ultimately results in a SSRS report being shown, using Report Viewer 2010 (in server mode). The report has been coded with a parameter #id to allow the report to display the correct data for the selected item.
The reports dataset can return multiple rows where some of the data is displayed in a summary area at the top (not in the header section) for example a textbox would have the expression =FIRST(Fields!Address.Value, "dsMain"). The data returned is denormalized so Address will always be the same value. Which is why using FIRST() works. And the rest of the data is shown in a Tablix with grouping applied etc.
But now I'm looking to change this so users can select multiple items and therefore effectively show the report multiple times, but shown in the same report viewer control. The main requirement is to batch print the reports, so showing it in one report view control is important to allow for one click printing of everything.
Now because I didn't design the report in the first place and because its fairly complex in its layout and the sql that is executed; the sql is geared towards running for one id and not a list of them. I'm looking for options to not have to rewrite the report or the sql.
Is it possible to give the report viewer the id parameter as a list and let the report viewer execute same report for each id passed? - I know report parameter can accept multiple values but this isn't the same since the report will unintelligently pass the first value to my stored procedure but not repeat the report for the other values. Perhaps there's a setting in the report designer that allows it to repeat if it is passed multiple values?
Can someone suggest something else to get this working? Or is my only option to extend the report and sql to accept multiple id's and effectively redesign the report?
Thanks any suggestions or help with this.
The answer is to use sub-reports.
Create a new report that takes a list of ids as a multi valued parameter.
Use that parameter as the dataset for a list control.
Have a subreport inside the list. Report inside the list is your original report.
You can then pass each element of your dataset(your list of parameters) as parameter to the your sub-report.
SSRS will repeat it as your want.
I have a report which has 3 subreports. In the case of no data I want to hide the report. It's giving me this error:
Error: Subreport could not be shown
How can I hide the subreports?
You are going to have to create some mechanism of knowing whether or not a subreport will successfully be shown on the main report because you aren't going to be able to "return" anything back to the main report from the subreport.
Could you create a small dataset on your main report that would query to check if data will exists for the subreport? and then you could use an expression on the subreport element (or container such as tablix or rectangle) to hide it based upon the results of the query on the main report.
Let me know if I need to clarify.
if we directly create a dataset in the main report itself then there is no question of using another report as a subreport we can directly use the fields from the data set created in the main report and assigning parameters to main dataset values. i think that will not server purpose.