The new 11g Bi Publisher has changed substantially as Oracle has provided a more lightweight approach, which all in all has it's benefits, though from a developers perspective has changed to the approach completely.
There was a setting within BI 10g, which allowed you to select CSV as a probable format, though within BI 11g, it seems that the product will make it's own judgement on which formats are available based on the report layout.
The steps below highlight the required changes to allow CSV as a possible format to export.
For each report there's an _report.xdo file that contains the XML structure of the report. The typical location of the report is as follows:
$WEBLOGIC_HOME / $BI_HOME /config/bipublisher/repository/Reports/ $ACTUAL_REPORT_NAME.xdo/_report.xdo
Within the OutputFormat node are all the possible formats that you can display within BI Publisher. After the last
format, add the value csv.
You can also change the Default value to csv though this is only recommended if the report does not require any further
input (no dates, no string values etc).
Next thing to do is bounce the WLS server for the changes to take effect
Now log back into BI publisher and select the report. You should now be able to see that CSV is now an option. When selected, this will automatically prompt you with the option to view this within MS excel.
About the author
Daniel is a Technical Manager with over 10 years of consulting expertise in the Identity and Access Management space.Daniel has built from scratch this blog as well as technicalconfessions.com
Follow Daniel on twitter @nervouswiggles
Comments
Other Posts
AS I was migrating my environment into an S3 environment, I wanted to leverage off the SES services that AWS provide, more specifically, to leverage the off the SMTP functionality by sending an email via PHP
Read More...
The WeMos D1 is a ESP8266 WiFi based board is an extension to the current out-of-the-box library that comes with the Arduino installation. Because of this, you need to import in the libraries as well as acknowledging the specific board. This process is highly confusion with a number of different individuals talking about a number of different ways to integrate.
Read More...
NameID element must be present as part of the Subject in the Response message, please enable it in the IDP configuration.
Read More...
For what I see, there's not too many supportive documentations out there that will demonstrate how provision AD group membership with the ICF connector using OpenIDM. The use of the special ldapGroups attribute is not explained anywhere in the Integrators guides to to the date of this blog. This quick blog identifies the tasks required to provision AD group membership from OpenIDM to AD using the LDAP ICF connector. However this doesn't really explain what ldapGroups actually does and there's no real worked example of how to go from an Assignment to ldapGroups to an assigned group in AD. I wrote up a wiki article for my own reference: AD group memberships automatically to users This is just my view, others may disagree, but I think the implementation experience could be improved with some more documentation and a more detailed example here.
Read More...
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...
org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...
ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...
When performing the attempt of a reconciliation from ForgeRock IDM to Active Directory, I would get the following error
Read More...
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...
During the reconcilation from OpenIDM to the ICF google apps connector, the following error response would occur. ERROR Caused by com.google.api.client.auth.oauth2.TokenResponseException 400 Bad Request - invalid_grant
Read More...
Tags
Recent Posts
Monthly Activity
Group by date