WebiPrompt problem: no data to fetch ("your parameter here": no given values)

[Former Member]

I am new to SAP Business Objects and am having trouble running a report that has parameters.  Specifically I am trying to execute a Web Intelligence Document that has WebiPrompts.

When I execute my program i get the following error:

no data to fetch ("pmTWIA": no given values)

In my code execution I can see that I am passing the xml with the prompts populated AND that when I look at the history for my Web Intelligence document that parameters have been passed.

Please see my java code attachment, debug output, and screen shot for more details

Java_output.txt.zip

Java_code.txt.zip

[Former Member · Accepted solution]

Hi Sean,

Please let us know the  BO product version with patches(if any)

What happens if you schedule the report directly from BILaunchpad/CMC with same parameter values?

Thanks,

Prithvi

[Former Member · Accepted solution]

Prithvi,

Thanks so much for the quick reply!!

We are running version:

SAP BusinessObjects BI Platform 4.1 Support Pack 4

Version: 14.1.4.1327

We scheduled the report from BILaunchpad with the same prompts and it works fine.  Attached is the history for the report.  The first screenshot shows the results from BILaunchpad and the second screenshot shows the results from running the report with the Java SDK where it fails.

Also attached is the latest code.  The only changes were to the dates that were used; otherwise its the same.

Any help would greatly be appreciated.

Thanks,

Sean

Java_code.txt.zip

Java_output.txt.zip

[Former Member · Accepted solution]

Hi Sean,

Thanks for letting us know the BO Product version.

For scheduling webi reports with prompts, the only supported way is to use Restful webservices SDKs.

The feature of scheduling a webi report with prompts were deprected from release BI 4.x and introduced in the new restfull webservices. Restful is the future which SAP is focussing and would be great to have your application on supported terms with SAP. 

You can get details about the restful webservices from the documents and blogs available at below forum

http://scn.sap.com/community/restful-sdk

You might get the old sdks to work implementing few workarounds, however the best move forward would be to move towards Restful Webservices as it is the future to move ahead with.

Please refer to the below document to find related information about Restful Webservices sdks.

http://scn.sap.com/docs/DOC-43224

http://scn.sap.com/docs/DOC-56658

The Developers guide can be found from

http://help.sap.com/bobip41?current=analytics#section7

Thanks,

Prithvi

[Former Member · Accepted solution]

Hi Prithvi,

Even with RESTful webservice, I am facing the same issue. please suggest.

I am trying to schedule a report as below with POST method with request body having the parameters.

https://<base-URL>/biprws/raylight/v1/documents/<reportID>/schedules

When submitting the request, I got the success msg as below -

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<success>

  <message>The resource of type 'Schedule' with identifier '1110314' has been successfully created.</message>

  <id>1110314</id>

</success>

But, when checked the same in BI Launch pad, it is failing with error,

Error Message:

no data to fetch ("Trend By": no given values)

I gave the proper value for parameter "Trend By".

If I try scheduling the report from BI Launch pad with same prompts , it works fine.

[Former Member · Accepted solution]

Rekha,

What does the xml look like when you do:

https://<base-URL>/biprws/raylight/v1/documents/<reportID>/parameters

Please post that XML here along with the XML you POST when actually scheduling the report.  Some parameter types are a little tricky and the API doesn't provide you much feedback about what went wrong.

Sean

[Former Member · Accepted solution]

Hi Sean,

Thanks for your immediate reply.

After comparing the xml which I got from the GET req above (/parameters) with my xml, I realised that the dataProviders ID (dpId) were not proper in my xml. It worked after changing the same.

Thanks again. You saved my time.

Rekha.