Finance | Project Operations, Human Resources, ...

ISV report data provider classes are not visible in visual studio

(0) Share

Report

Posted on by FlorinF

Hello !

I have an ISV report data provider class that I want to use in my report.

The ISV is installed as binary package.

The problem is that in visual studio, in the report designer, if I browse for data providers I can't see any data provider from this package.

I can see only standard data providers, nothing from my ISV binary package

This data provider is completely new , is not an extension of the standard one it is designed from scratch: public class SalesInvoiceDP_xx extends SrsReportDataProviderPreProcess

Do I need to refresh something ?

1663.A.png 8836.B.png

I have the same question (0)

All responses (11)

Answers (0)

André Arnaud de Cal... 300,911 Super User 2025 Season 2 on at

Like (0)

Report

Hi FlorinF,

When the ISV did deliver only the binary package, you can't see the coding; only the references. In the AOT, the object names are then displayed in italic font. You can extend the ISV class like any other class.

Was this reply helpful? Yes No
FlorinF on at

Like (0)

Report

Hi André Arnaud de Calavon,

I have the code, I'm actually the one that created that package.

Even If I put the code in dev box of the client, Visual Studio doesn't see the any of the data providers of that model.

if you try to refresh the data source you get an error like this, even if the temp table exists in the model:

And if you want to browse for data sources, you don't see data providers from this model. I was expecting that VS use meta data service to retrieve the classes that implement SRSReportDataProvider interface, binary or not.

If you manually put the values in the query of the data provider, the VS will refresh the columns of the DS from the ISV table

It's an inconsistency here... it works if you do it manually.

Was this reply helpful? Yes No
André Arnaud de Cal... 300,911 Super User 2025 Season 2 on at

Like (0)

Report

Hi Florin,

Is it working in your DEV environment and are all related objects part of the package? What type of environment do you have the issue?

Was this reply helpful? Yes No
FlorinF on at

Like (0)

Report

The issue is on the customer dev box, where I install the binary package. It's working if you manually change the query

Was this reply helpful? Yes No
Suggested answer

greengrimms 1,400 on at

Like (0)

Report

Hi Florin,

So the issue is there because you only installed binaries in your customer's dev-box. Even if you're the solution provider, you won't see any source code since it's not included in the deployable package.

Specifically for this, you could simply work on your own dev machine where you can access the ISV code.

Was this reply helpful? Yes No
FlorinF on at

Like (0)

Report

Hi,

I actually have the source code of the ISV on client dev box for debugging purposes. The source code is not the issue.

The problem is how Visual Studio/Reporting services reads the metadata from AOT. I was expecting that VS use the meta data service to retrieve the classes/objects that implement SRSReportDataProvider interface, after the models are compiled to .NET libraries. It should not matter how the ISV is installed as long it compiles to .NET dll. This is a bug regarding integration between AOT and Reporting services.

Was this reply helpful? Yes No
Suggested answer

greengrimms 1,400 on at

Like (0)

Report

Yes, I think I'm following. Had a similar issue and I had to remove the binaries for the ISV in the environment, move the source code there, and compile. After that, it was working correctly.

Also, it doesn't hurt to do a Model refresh from Dynamics 365 > Model management menu.

Was this reply helpful? Yes No
Suggested answer

Joris dG 17,775 on at

Like (0)

Report

I'm not sure I understand the issue. It is true the reporting tools asks the AOS for details, it doesn't read code from Visual Studio. The main reason for this has to do with system fields that aren't represented in the metadata directly.

In any case, I'm not sure how it matters how binaries are deployed... Assuming your ISV code is showing up in F&O client, the reporting services should be able to also see all it needs...

did you perhaps install the package from command line with a quick install, but not dbsync&restart the AOS?

Was this reply helpful? Yes No
FlorinF on at

Like (0)

Report

Hi Joris de Gruyter

Ture, the package has been installed from command line with devinstall parametter but I did dbsync and the machine has been restarted many times. The reporting tool should read from the AOT via metadata services, the objects implementing SRSReportDataProvider. Somehow is not able to do so for binary packages installed.

Also is not working if you simply create a child class (not extension) of the ISV data provider class. You need to

override the "getTable" method like this in order be picked by reporting tools

public class CUST_DPclass extends ISV_DPclass

{

[SRSReportDataSetAttribute(tableStr(ISVTableTmp))]

public ISVTableTmpget geTable()

{

select ISVTableTmp;

return ISVTableTmp;

}

}

If you compile the code above in the customization model, the CUST_DPclass will picked by the reporting but is not the same thing: this is not in the ISV model anymore.

It's not specific only to my dev box, I've got a confirmation on yammer group that report designer does not allow you to select a binary-only class, however it seems to work OK if you type in the query yourself - i.e. SELECT * FROM ClassName.TableName.

Was this reply helpful? Yes No
Joris dG 17,775 on at

Like (0)

Report

And you're saying if you put the ISV source code on, it works? or you have to put the source code on the box, then recompile, then it works?

Was this reply helpful? Yes No