How to use a SQL View for just one or two text boxes in Acumatica Report Designer without affecting other data

​@tahayabali The best practice for something like this is to use a subreport. Whichever joins would be used to add the view to the main report, instead use them as collection parameters for the subreport and populate the fields within the subreport. Have you already tried something like this?

​@BenjaminCrisman I have never work on sub reports. 

If I go with the subreport approach, can you guide me on the exact logic for passing both conditions?
For example, my main requirement is to take results from the view where t is less than 0.7576 into one text box, and where it is greater than or equal to 0.7576 into another.

How should I structure the parameters or variables so the subreport returns the correct value for each case without affecting my main report’s existing relations?
 

​@tahayabali The subreport is just another report embedded into the main report, so you would create the separate report first, which will be the subreport, and add your SQL view/DAC to that report and setup the text boxes like you need them to return the data.

Then in the main report you would add the subreport element to the area you want to display the subreport data. The next thing would be to add the Collection Parameters which would be the joins that you would use if you were adding the view/dac to your report:

The ValueExpr would contain them like =[ARInvoice.DocType] or =[@DocType] if you want them to collect the parameter entered when the user runs the report.

Then you can add the ReportName which would be your subreport file name like ar809000sub1.rpx

​@BenjaminCrisman I have created the sub report. The query is working fine in SQL and returning me data. But Report is printing empty data for the same query.