Loads in Power BI Report Builder, not in Power BI Service

[Anonymous]

I have a report which was built in Report Builder 3.0 (on our outdated 2008 R2 Server) to which I updated in Power BI Report Builder (v15.7.1797.84). I can run the report in Power BI Report Builder without issues, data loads (see below); however, when I publish to my Power BI Service (Premium Per User subscription), I get the infamous "Unable to render paginated report" (see below) without much of a description as to exactly what caused this. I have a few reports which are starting to do this and trying to figure out what's triggering this when it loads in Report Builder, but not Service. I've clicked on the elipse on the report within Power BI Service > Manage and ensured the "Data sources included in this dataset" is green and the status is showing a green check mark under the Gateway Connection section. Is there any way to dig deeper into the "Unable to Render Paginated Report" and figure out exactly which "field" it's refering to?

[Anonymous]

It appears to be my date parameters within my query it doesn't like.

within the query:

AND ORIGPOSTDATE BETWEEN :pStartDate AND :pEndDate

dsDefaultDates:

select trunc(sysdate-1) StartDate,
trunc(sysdate-1) EndDate
from dual

If I try and cast it as a date, then I get the below error:

AND ORIGPOSTDATE BETWEEN to_date(:pStartDate, 'mm-dd-yyyy') and to_date(:pEndDate, 'mm-dd-yyyy')

[Anonymous]

I've mixed and match my date parameter within my query to either cast, not cast as a date, to use "to_date()"....nothing seems to work. I've also tried the below as well:

within query:

AND ORIGPOSTDATE BETWEEN :pStartDate AND :pEndDate

DS Properties:

Start and Stop date Expression(s):

Then when I run the report I get the following error:

[GilbertQ]

yeah for sure I find it is the quickest way to get it done!

[GilbertQ]

Hi @Anonymous 

The only way to resolve this is to start with a single value and keep on adding them until you get the error. I know it is not the greatest answer but that is what I would do to troubleshoot and identify the issue.

[Anonymous]

Darn, was hoping for a little better solution. But understandable, I'll go through the long process of putting everything back 1 at a time until the culprit is revealed. Thank you!